diff options
| author | Shashank Balaji <[email protected]> | 2025-05-27 12:59:09 +0000 |
|---|---|---|
| committer | Rafael J. Wysocki <[email protected]> | 2025-06-18 19:33:01 +0000 |
| commit | 2e1185c9d7b4f890614e891ae1414653b35b88e3 (patch) | |
| tree | 5db3f72ed64f6f8bb962ae6c2a79deab653c28ef /rust/helpers/mutex.c | |
| parent | cpufreq: CPPC: Remove forward declaration of cppc_cpufreq_register_em() (diff) | |
| download | kernel-2e1185c9d7b4f890614e891ae1414653b35b88e3.tar.gz kernel-2e1185c9d7b4f890614e891ae1414653b35b88e3.zip | |
cpufreq: userspace: set CPUFREQ_GOV_STRICT_TARGET flag
When the userspace governor is used, the user intends to set a fixed CPU
frequency for a policy, for whatever reason. The CPUFREQ_GOV_STRICT_TARGET
flag is the required behaviour. Without this flag, the intel_pstate driver,
with HWP enabled, will set HWP_MIN_PERF to the target frequency and
HWP_MAX_PERF to the policy maximum, when configuring the HWP_REQUEST MSR.
This lets the hardware choose any frequency between the target frequency
and the policy maximum, which is not the intended behaviour. To fix this,
`cat scaling_setspeed > scaling_max_freq` had to be done. With this patch,
that is no longer necessary. Setting scaling_setspeed is sufficient, as
expected.
Signed-off-by: Shashank Balaji <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'rust/helpers/mutex.c')
0 files changed, 0 insertions, 0 deletions