aboutsummaryrefslogtreecommitdiff
path: root/block/blk-settings.c
diff options
context:
space:
mode:
authorViresh Kumar <viresh.kumar@linaro.org>2012-12-14 11:13:45 +0530
committerViresh Kumar <viresh.kumar@linaro.org>2013-01-12 10:41:00 +0530
commit3960872935b76f177a4169cb6ce135b54d30bc50 (patch)
tree786ba3c903da25b821d5eae6f3056aa4aa3cc2e4 /block/blk-settings.c
parent6def83ce4bb23170d9c4fdf7a7105b90d3cb73b7 (diff)
downloadvexpress-lsk-3960872935b76f177a4169cb6ce135b54d30bc50.tar.gz
cpufreq: Don't use cpu removed during cpufreq_driver_unregister
This is how the core works: cpufreq_driver_unregister() - subsys_interface_unregister() - for_each_cpu() call cpufreq_remove_dev(), i.e. 0,1,2,3,4 when we unregister. cpufreq_remove_dev(): - Remove policy node - Call cpufreq_add_dev() for next cpu, sharing mask with removed cpu. i.e. When cpu 0 is removed, we call it for cpu 1. And when called for cpu 2, we call it for cpu 3. - cpufreq_add_dev() would call cpufreq_driver->init() - init would return mask as AND of 2, 3 and 4 for cluster A7. - cpufreq core would do online_cpu && policy->cpus Here is the BUG(). Because cpu hasn't died but we have just unregistered the cpufreq driver, online cpu would still have cpu 2 in it. And so thing go bad again. Solution: Keep cpumask of cpus that are registered with cpufreq core and clear cpus when we get a call from subsys_interface_unregister() via cpufreq_remove_dev(). Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Diffstat (limited to 'block/blk-settings.c')
0 files changed, 0 insertions, 0 deletions