diff options
| author | Rafael J. Wysocki <[email protected]> | 2025-06-16 18:19:19 +0000 |
|---|---|---|
| committer | Rafael J. Wysocki <[email protected]> | 2025-07-14 17:36:43 +0000 |
| commit | 1cefe495cacba5fb0417da3a75a1a76e3546d176 (patch) | |
| tree | 1f266ded071192e91b8798b2858e7af898718e87 /rust/helpers/helpers.c | |
| parent | cpufreq: docs: userspace: Explain HW coordination influence (diff) | |
| download | kernel-1cefe495cacba5fb0417da3a75a1a76e3546d176.tar.gz kernel-1cefe495cacba5fb0417da3a75a1a76e3546d176.zip | |
cpufreq: intel_pstate: Always use HWP_DESIRED_PERF in passive mode
In the passive mode, intel_cpufreq_update_pstate() sets HWP_MIN_PERF in
accordance with the target frequency to ensure delivering adequate
performance, but it sets HWP_DESIRED_PERF to 0, so the processor has no
indication that the desired performance level is actually equal to the
floor one. This may cause it to choose a performance point way above
the desired level.
Moreover, this is inconsistent with intel_cpufreq_adjust_perf() which
actually sets HWP_DESIRED_PERF in accordance with the target performance
value.
Address this by adjusting intel_cpufreq_update_pstate() to pass
target_pstate as both the minimum and the desired performance levels
to intel_cpufreq_hwp_update().
Fixes: a365ab6b9dfb ("cpufreq: intel_pstate: Implement the ->adjust_perf() callback")
Signed-off-by: Rafael J. Wysocki <[email protected]>
Tested-by: Shashank Balaji <[email protected]>
Link: https://patch.msgid.link/[email protected]
Diffstat (limited to 'rust/helpers/helpers.c')
0 files changed, 0 insertions, 0 deletions
