Ashok Raj 90d45d17f3 [PATCH] cpu hotplug: fix locking in cpufreq drivers ... When calling target drivers to set frequency, we take cpucontrol lock. When we modified the code to accomodate CPU hotplug, there was an attempt to take a double lock of cpucontrol leading to a deadlock. Since the current thread context is already holding the cpucontrol lock, we dont need to make another attempt to acquire it. Now we leave a trace in current->flags indicating current thread already is under cpucontrol lock held, so we dont attempt to do this another time. Thanks to Andrew Morton for the beating:-) From: Brice Goglin <Brice.Goglin@ens-lyon.org> Build fix (akpm: this patch is still unpleasant. Ashok continues to look for a cleaner solution, doesn't he? ;)) Signed-off-by: Ashok Raj <ashok.raj@intel.com> Signed-off-by: Brice Goglin <Brice.Goglin@ens-lyon.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>		2005-11-09 07:55:50 -08:00
..
cpufreq_conservative.c
cpufreq_ondemand.c
cpufreq_performance.c
cpufreq_powersave.c
cpufreq_stats.c	Merge master.kernel.org:/pub/scm/linux/kernel/git/davej/cpufreq	2005-11-07 13:28:20 -08:00
cpufreq_userspace.c
cpufreq.c	[PATCH] cpu hotplug: fix locking in cpufreq drivers	2005-11-09 07:55:50 -08:00
freq_table.c
Kconfig
Makefile