Bug 217618
Summary: | Changing maximum frequency and boost state does not work with amd-pstate in passive mode plus the schedutil governor | ||
---|---|---|---|
Product: | Power Management | Reporter: | Prajna Sariputra (putr4.s) |
Component: | cpufreq | Assignee: | linux-pm (linux-pm) |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | CC: | Perry.Yuan, ray.huang |
Priority: | P3 | ||
Hardware: | AMD | ||
OS: | Linux | ||
Kernel Version: | 6.4.0 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Prajna Sariputra
2023-07-01 08:21:17 UTC
Hi Sariputra, thank you for reporting this issue, could you let me know the values of your system? # cat /sys/devices/system/cpu/cpu*/cpufreq/amd_pstate_max_freq # cat /sys/devices/system/cpu/cpu*/acpi_cppc/highest_perf Perry. Here is the output of the first command: 4785000 4785000 4785000 4785000 4785000 4785000 4785000 4785000 4785000 4785000 4785000 4785000 4785000 4785000 4785000 4785000 And here is the output for the second one: 191 196 196 166 166 186 186 191 181 181 176 176 196 196 171 171 Thanks for your info share, I guess the boost and scaling_max have something need to be improved when user try to limit the max frequency. I have implemented a new boost control with a patchset that are under internal viewing. it works for both the passive and active mode. With kernel 6.9.0, it looks like limiting the frequency control now works in both active and passive mode, and in the latter case both the schedutil and ondemand governors respect the frequency limit, so this appears to be fixed for me, thanks! (In reply to Prajna Sariputra from comment #5) > With kernel 6.9.0, it looks like limiting the frequency control now works in > both active and passive mode, and in the latter case both the schedutil and > ondemand governors respect the frequency limit, so this appears to be fixed > for me, thanks! good to know that. thanks for your feedback. Perry. |