diff options
author | 2024-12-06 23:20:04 -0600 | |
---|---|---|
committer | 2025-03-06 13:01:24 -0600 | |
commit | 6f0b13f16f7a214996a8a125080a6a99bda5d1f7 (patch) | |
tree | 6767f07376d1b3ed06e1c96273ee1b1db6f9b239 /scripts/lib/kdoc/kdoc_re.py | |
parent | cpufreq/amd-pstate: Move perf values into a union (diff) | |
download | wireguard-linux-6f0b13f16f7a214996a8a125080a6a99bda5d1f7.tar.xz wireguard-linux-6f0b13f16f7a214996a8a125080a6a99bda5d1f7.zip |
cpufreq/amd-pstate: Overhaul locking
amd_pstate_cpu_boost_update() and refresh_frequency_limits() both
update the policy state and have nothing to do with the amd-pstate
driver itself.
A global "limits" lock doesn't make sense because each CPU can have
policies changed independently. Each time a CPU changes values they
will atomically be written to the per-CPU perf member. Drop per CPU
locking cases.
The remaining "global" driver lock is used to ensure that only one
entity can change driver modes at a given time.
Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
Reviewed-by: Dhananjay Ugwekar <dhananjay.ugwekar@amd.com>
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_re.py')
0 files changed, 0 insertions, 0 deletions