[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240901050035.1739935-1-superm1@kernel.org>
Date: Sun, 1 Sep 2024 00:00:33 -0500
From: Mario Limonciello <superm1@...nel.org>
To: "Gautham R . Shenoy" <gautham.shenoy@....com>,
Perry Yuan <perry.yuan@....com>
Cc: linux-kernel@...r.kernel.org (open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)),
linux-pm@...r.kernel.org (open list:CPU FREQUENCY SCALING FRAMEWORK),
Mario Limonciello <mario.limonciello@....com>
Subject: [PATCH 0/2] amd-pstate: Better handling for systems without an MSR
From: Mario Limonciello <mario.limonciello@....com>
Since the policy changed for amd-pstate to enable on systems
with shared memory designs by default too some users have
reported that software like power-profiles-daemon fails
with an error -524.
This happens because error codes from the CPPC API are ignored
during the initial setup so all the sysfs files are created but
don't work.
This series does two things:
1. Add a debugging early param to force going into shared memory mode
even on a system with a dedicated MSR. This will aid in debugging
reported issues.
2. Catch errors in amd_pstate_epp_update_limit() and pass them up. If
any errors occurred with CPPC API then amd-pstate won't be setup.
Mario Limonciello (2):
cpufreq/amd-pstate: Add an early param to disable MSR mode
cpufreq/amd-pstate: Catch failures for amd_pstate_epp_update_limit()
.../admin-guide/kernel-parameters.txt | 5 ++-
Documentation/admin-guide/pm/amd-pstate.rst | 5 +++
drivers/cpufreq/amd-pstate.c | 43 +++++++++++++------
3 files changed, 38 insertions(+), 15 deletions(-)
--
2.43.0
Powered by blists - more mailing lists