As a consequence of commit 49388f11d512bb92706ce
("x86/cpufreq: relocate the driver register function")
the cpufreq CPU notifier was being registered twice.
That resulted in bugs when trying to offline a
CPU, as reported here:https://www.mail-archive.com/xen-devel@lists.xen.org/msg41618.html Signed-off-by: Dario Faggioli <dario.faggi...@citrix.com> --- Cc: Jan Beulich <jbeul...@suse.com> Cc: Andrew Cooper <andrew.coop...@citrix.com> Cc: "Wang, Wei W" <wei.w.w...@intel.com> Cc: Konrad Rzeszutek Wilk <konrad.w...@oracle.com> --- xen/drivers/cpufreq/cpufreq.c | 1 - 1 file changed, 1 deletion(-) diff --git a/xen/drivers/cpufreq/cpufreq.c b/xen/drivers/cpufreq/cpufreq.c index 81a187b..6e666e4 100644 --- a/xen/drivers/cpufreq/cpufreq.c +++ b/xen/drivers/cpufreq/cpufreq.c @@ -650,6 +650,5 @@ int __init cpufreq_register_driver(struct cpufreq_driver *driver_data) cpufreq_driver = driver_data; - register_cpu_notifier(&cpu_nfb); return 0; } _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
