diff options
author | 2013-07-02 16:36:28 +0530 | |
---|---|---|
committer | 2013-07-04 13:12:44 +0200 | |
commit | 266c13d767be61a17d8e6f2310b9b7c46278273b (patch) | |
tree | 924a27434d5846f69b541012494d6ea1f2cb10cf /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | Merge tag 'pm+acpi-3.11-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm (diff) | |
download | linux-dev-266c13d767be61a17d8e6f2310b9b7c46278273b.tar.xz linux-dev-266c13d767be61a17d8e6f2310b9b7c46278273b.zip |
cpufreq: Fix serialization of frequency transitions
Commit 7c30ed ("cpufreq: make sure frequency transitions are serialized")
interacts poorly with systems that have a single core freqency for all
cores. On such systems we have a single policy for all cores with
several CPUs. When we do a frequency transition the governor calls the
pre and post change notifiers which causes cpufreq_notify_transition()
per CPU. Since the policy is the same for all of them all CPUs after
the first and the warnings added are generated by checking a per-policy
flag the warnings will be triggered for all cores after the first.
Fix this by allowing notifier to be called for n times. Where n is the number of
cpus in policy->cpus.
Reported-and-tested-by: Mark Brown <broonie@linaro.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions