cpufreq: Do not update related_cpus on every policy activation
authorRafael J. Wysocki <rafael.j.wysocki@intel.com>
Mon, 27 Jul 2015 21:11:44 +0000 (23:11 +0200)
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>
Tue, 28 Jul 2015 15:24:12 +0000 (17:24 +0200)
commit4d1f3a5bcb489cc6f7cbc128e0c292fed7868d32
tree0a766959c4d5c1000bb6e29d970087a4b2982cd9
parentd9612a495b0bc93f5db0e0033fe4ee7abb7167c7
cpufreq: Do not update related_cpus on every policy activation

The related_cpus mask includes CPUs whose cpufreq_cpu_data per-CPU
pointers have been set the the given policy.  Since those pointers
are only set at the policy creation time and unset when the policy
is deleted, the related_cpus should not be updated between those
two operations.

For this reason, avoid updating it whenever the first of the
"related" CPUs goes online.

Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
drivers/cpufreq/cpufreq.c