summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/bpf/prog_tests
diff options
context:
space:
mode:
authorFrancisco Jerez <currojerez@riseup.net>2020-08-31 20:02:50 -0700
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2020-09-01 21:15:00 +0200
commiteacc9c5a927e474c173a5d53dd7fb8e306511768 (patch)
tree52ca3f6613f7843c004f2227ac70eca954b52d45 /tools/testing/selftests/bpf/prog_tests
parent55671ea3257ac596abd817c4031a996b2867e586 (diff)
downloadlinux-eacc9c5a927e474c173a5d53dd7fb8e306511768.tar.gz
linux-eacc9c5a927e474c173a5d53dd7fb8e306511768.tar.bz2
linux-eacc9c5a927e474c173a5d53dd7fb8e306511768.zip
cpufreq: intel_pstate: Fix intel_pstate_get_hwp_max() for turbo disabled
This fixes the behavior of the scaling_max_freq and scaling_min_freq sysfs files in systems which had turbo disabled by the BIOS. Caleb noticed that the HWP is programmed to operate in the wrong P-state range on his system when the CPUFREQ policy min/max frequency is set via sysfs. This seems to be because in his system intel_pstate_get_hwp_max() is returning the maximum turbo P-state even though turbo was disabled by the BIOS, which causes intel_pstate to scale kHz frequencies incorrectly e.g. setting the maximum turbo frequency whenever the maximum guaranteed frequency is requested via sysfs. Tested-by: Caleb Callaway <caleb.callaway@intel.com> Signed-off-by: Francisco Jerez <currojerez@riseup.net> Acked-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> [ rjw: Minor subject edits ] Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests')
0 files changed, 0 insertions, 0 deletions