summaryrefslogtreecommitdiffstats
path: root/virt/kvm
diff options
context:
space:
mode:
authorViresh Kumar <viresh.kumar@linaro.org>2015-02-19 17:02:06 +0530
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2015-05-07 23:36:41 +0200
commitbb29ae152e3b9d79ca35e41945a55b616e91b5b9 (patch)
tree9c2c5c547a142ffc6f005d617cfb1715ad0989db /virt/kvm
parent1b947c904c4831d787c1f17a6a6cd40c7144ba85 (diff)
downloadop-kernel-dev-bb29ae152e3b9d79ca35e41945a55b616e91b5b9.zip
op-kernel-dev-bb29ae152e3b9d79ca35e41945a55b616e91b5b9.tar.gz
cpufreq: Keep a single path for adding managed CPUs
There are two cases when we may try to add CPUs we're already handling: - On boot, the first cpu has marked all policy->cpus managed and so we will find policy for all other policy->cpus later on. - When a managed cpu is hotplugged out and later brought back in. Currently, separate paths and checks take care of the two. While the first one is detected by testing cpu against 'policy->cpus', the other one is detected by testing cpu against 'policy->related_cpus'. We can handle them both via a single path and there is no need to do special checking for the first one. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org> Acked-by: Saravana Kannan <skannan@codeaurora.org> [ rjw: Changelog, comments ] Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud