diff options
author | 2025-01-17 18:14:56 +0800 | |
---|---|---|
committer | 2025-01-23 21:06:33 +0100 | |
commit | 03d8b4e76266e11662c5e544854b737843173e2d (patch) | |
tree | af581d6a78c58813761f7f5231cbd8e6cd9fa1f6 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | cpufreq: Introduce a more generic way to set default per-policy boost flag (diff) | |
download | wireguard-linux-03d8b4e76266e11662c5e544854b737843173e2d.tar.xz wireguard-linux-03d8b4e76266e11662c5e544854b737843173e2d.zip |
cpufreq: CPPC: Fix wrong max_freq in policy initialization
In policy initialization, policy->max and policy->cpuinfo.max_freq are
always set to the value calculated from caps->nominal_perf.
This will cause the frequency stay on base frequency even if the policy
is already boosted when a CPU is going online.
Fix this by using policy->boost_enabled to determine which value should
be set.
Signed-off-by: Lifeng Zheng <zhenglifeng1@huawei.com>
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Link: https://patch.msgid.link/20250117101457.1530653-4-zhenglifeng1@huawei.com
[ rjw: Changelog edits ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions