Searched hist:"90 e41bac100e34f955f48e7686c2fc685ac9aa30" (Results 1 – 1 of 1) sorted by relevance
| /openbmc/linux/drivers/cpufreq/ |
| H A D | cpufreq.c | diff 90e41bac100e34f955f48e7686c2fc685ac9aa30 Thu Nov 12 08:18:46 CST 2009 Prarit Bhargava <prarit@redhat.com> [CPUFREQ] Fix stale cpufreq_cpu_governor pointer
Dave,
Attached is an update of my patch against the cpufreq fixes branch.
Before applying the patch I compiled and booted the tree to see if the panic
was still there -- to my surprise it was not. This is because of the conversion
of cpufreq_cpu_governor to a char[].
While the panic is kaput, the problem of stale data continues and my patch is
still valid. It is possible to end up with the wrong governor after hotplug
events because CPUFREQ_DEFAULT_GOVERNOR is statically linked to a default,
while the cpu siblings may have had a different governor assigned by a user.
ie) the patch is still needed in order to keep the governors assigned
properly when hotplugging devices
Signed-off-by: Prarit Bhargava <prarit@redhat.com>
Signed-off-by: Dave Jones <davej@redhat.com>
|