diff options
| author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2021-11-03 19:43:47 +0100 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2021-11-04 19:48:47 +0100 |
| commit | dbea75fe18f60e364de6d994fc938a24ba249d81 (patch) | |
| tree | 06b28b5ff13d302c1c99fa85424a45a3a86ed494 /kernel/latencytop.c | |
| parent | 833db72142b93a89211c1e43ca0a1e2e16457756 (diff) | |
| download | linux-next-dbea75fe18f60e364de6d994fc938a24ba249d81.tar.gz | |
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
->adjust_perf() callback") caused intel_pstate to use nonzero HWP
desired values in certain usage scenarios, but it did not prevent
them from being leaked into the confugirations in which HWP desired
is expected to be 0.
The failing scenarios are switching the driver from the passive
mode to the active mode and starting a new kernel via kexec() while
intel_pstate is running in the passive mode.
To address this issue, ensure that HWP desired will be cleared on
offline and suspend/shutdown.
Fixes: a365ab6b9dfb ("cpufreq: intel_pstate: Implement the ->adjust_perf() callback")
Reported-by: Julia Lawall <julia.lawall@inria.fr>
Tested-by: Julia Lawall <julia.lawall@inria.fr>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'kernel/latencytop.c')
0 files changed, 0 insertions, 0 deletions