summaryrefslogtreecommitdiffstats
path: root/arch/x86/kernel/entry_32.S
diff options
context:
space:
mode:
authorIngo Molnar <mingo@elte.hu>2009-01-12 10:49:53 +0100
committerIngo Molnar <mingo@elte.hu>2009-01-12 19:24:23 +0100
commit50c668d678fd01284799a6e4f1b91829d83cb9ed (patch)
treef3e129473515950d93a39b92c6ea2ebcbe3e5174 /arch/x86/kernel/entry_32.S
parent2bc1379712e74c5b99adaa6db433c14d8841ab4f (diff)
downloadop-kernel-dev-50c668d678fd01284799a6e4f1b91829d83cb9ed.zip
op-kernel-dev-50c668d678fd01284799a6e4f1b91829d83cb9ed.tar.gz
Revert "cpumask: use work_on_cpu in acpi-cpufreq.c for drv_read and drv_write"
This reverts commit 7503bfbae89eba07b46441a5d1594647f6b8ab7d. Dieter Ries reported bootup soft-hangs and bisected it back to this commit, and reverting this commit gave him a working system. The commit introduces work_on_cpu() use into the cpufreq code, but that is subtly problematic from a lock hierarchy POV: the hotplug-cpu lock is an highlevel lock that is taken before lowlevel locks, and in this codepath we are called with the policy lock taken. Dieter did not have lockdep enabled so we dont have a nice stack trace proof for this, but using work_on_cpu() in such a lowlevel place certainly looks wrong, so we revert the patch. work_on_cpu() needs to be reworked to be more generally usable. Reported-by: Dieter Ries <clip2@gmx.de> Tested-by: Dieter Ries <clip2@gmx.de> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch/x86/kernel/entry_32.S')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud