summaryrefslogtreecommitdiff
path: root/Documentation/filesystems/sysfs.txt
diff options
context:
space:
mode:
authorSebastian Andrzej Siewior <bigeasy@linutronix.de>2013-06-07 20:37:06 (GMT)
committerScott Wood <scottwood@freescale.com>2015-02-13 22:21:04 (GMT)
commit6adf6a40918b49ac563fb1db9b47eacb7925dd3f (patch)
treeabc5bda52eba26c261acb38f584b811c8eac9c5b /Documentation/filesystems/sysfs.txt
parente33f02dbe48761efd7022ceb10512daf7bd7b5a3 (diff)
downloadlinux-fsl-qoriq-6adf6a40918b49ac563fb1db9b47eacb7925dd3f.tar.xz
kernel/cpu: fix cpu down problem if kthread's cpu is going down
If kthread is pinned to CPUx and CPUx is going down then we get into trouble: - first the unplug thread is created - it will set itself to hp->unplug. As a result, every task that is going to take a lock, has to leave the CPU. - the CPU_DOWN_PREPARE notifier are started. The worker thread will start a new process for the "high priority worker". Now kthread would like to take a lock but since it can't leave the CPU it will never complete its task. We could fire the unplug thread after the notifier but then the cpu is no longer marked "online" and the unplug thread will run on CPU0 which was fixed before :) So instead the unplug thread is started and kept waiting until the notfier complete their work. Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Diffstat (limited to 'Documentation/filesystems/sysfs.txt')
0 files changed, 0 insertions, 0 deletions