Ingo Molnar 50c668d678 Revert "cpumask: use work_on_cpu in acpi-cpufreq.c for drv_read and drv_write" ... This reverts commit 7503bfbae8. 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>		2009-01-12 19:24:23 +01:00
..
boot	…
configs	…
crypto	…
ia32	…
include/asm	x86: fix apic.c build error on latest git	2009-01-12 19:24:23 +01:00
kernel	Revert "cpumask: use work_on_cpu in acpi-cpufreq.c for drv_read and drv_write"	2009-01-12 19:24:23 +01:00
kvm	…
lguest	…
lib	…
mach-default	…
mach-generic	…
mach-rdc321x	…
mach-voyager	…
math-emu	…
mm	x86: avoid theoretical vmalloc fault loop	2009-01-12 19:24:21 +01:00
oprofile	…
pci	…
power	…
scripts	…
vdso	…
video	…
xen	…
Kconfig	…
Kconfig.cpu	…
Kconfig.debug	…
Makefile	…
Makefile_32.cpu	…