diff options
author | 2021-01-12 13:21:27 +0800 | |
---|---|---|
committer | 2021-01-12 19:44:49 +0100 | |
commit | 6f67e060083a84a4cc364eab6ae40c717165fb0c (patch) | |
tree | 031978b05159489fd6609d7d1ab6673b593b6289 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | cpufreq: intel_pstate: Rename two functions (diff) | |
download | wireguard-linux-6f67e060083a84a4cc364eab6ae40c717165fb0c.tar.xz wireguard-linux-6f67e060083a84a4cc364eab6ae40c717165fb0c.zip |
cpufreq: intel_pstate: Get per-CPU max freq via MSR_HWP_CAPABILITIES if available
Currently, when turbo is disabled (either by BIOS or by the user),
the intel_pstate driver reads the max non-turbo frequency from the
package-wide MSR_PLATFORM_INFO(0xce) register.
However, on asymmetric platforms it is possible in theory that small
and big core with HWP enabled might have different max non-turbo CPU
frequency, because MSR_HWP_CAPABILITIES is per-CPU scope according
to Intel Software Developer Manual.
The turbo max freq is already per-CPU in current code, so make
similar change to the max non-turbo frequency as well.
Reported-by: Wendy Wang <wendy.wang@intel.com>
Signed-off-by: Chen Yu <yu.c.chen@intel.com>
[ rjw: Subject and changelog edits ]
Cc: 4.18+ <stable@vger.kernel.org> # 4.18+: a45ee4d4e13b: cpufreq: intel_pstate: Change intel_pstate_get_hwp_max() argument
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions