diff options
author | 2024-03-28 19:52:45 +0100 | |
---|---|---|
committer | 2024-04-02 12:57:22 +0200 | |
commit | e8217b4bece379e66d43ab5070431712f07bf625 (patch) | |
tree | d58170f7b0f30037e30cc33f141fbe6ee03f7989 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | cpufreq: intel_pstate: Replace three global.turbo_disabled checks (diff) | |
download | wireguard-linux-e8217b4bece379e66d43ab5070431712f07bf625.tar.xz wireguard-linux-e8217b4bece379e66d43ab5070431712f07bf625.zip |
cpufreq: intel_pstate: Update the maximum CPU frequency consistently
There are 3 places at which the maximum CPU frequency may change,
store_no_turbo(), intel_pstate_update_limits() (when called by the
cpufreq core) and intel_pstate_notify_work() (when handling a HWP
change notification). Currently, cpuinfo.max_freq is only updated by
store_no_turbo() and intel_pstate_notify_work(), although it principle
it may be necessary to update it in intel_pstate_update_limits() either.
Make all of them mutually consistent.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions