From: Mario Limonciello <mario.limonciello@amd.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>
Subject: second round of amd-pstate changess for 6.12 (second try)
Date: Wed, 11 Sep 2024 11:01:23 -0500 [thread overview]
Message-ID: <0f490e10-bab5-44d2-aa9f-efd80d306083@amd.com> (raw)
The following changes since commit 6b612d1bac67b0f483fde7779a45f6310274d4eb:
cpufreq: ti-cpufreq: Use socinfo to get revision in AM62 family
(2024-09-04 20:43:59 +0530)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git
tags/amd-pstate-v6.12-2024-09-11
for you to fetch changes up to
93497752dfed196b41d2804503e80b9a04318adb:
cpufreq/amd-pstate-ut: Fix an "Uninitialized variables" issue
(2024-09-11 10:53:03 -0500)
----------------------------------------------------------------
second round of amd-pstate changes for 6.12 (second try):
* Move the calculation of the AMD boost numerator outside of
amd-pstate, correcting acpi-cpufreq on systems with preferred cores
* Harden preferred core detection to avoid potential false positives
* Add extra unit test coverage for mode state machine
----------------------------------------------------------------
Mario Limonciello (13):
x86/amd: Move amd_get_highest_perf() from amd.c to cppc.c
ACPI: CPPC: Adjust return code for inline functions in
!CONFIG_ACPI_CPPC_LIB
x86/amd: Rename amd_get_highest_perf() to
amd_get_boost_ratio_numerator()
ACPI: CPPC: Drop check for non zero perf ratio
ACPI: CPPC: Adjust debug messages in amd_set_max_freq_ratio() to warn
x86/amd: Move amd_get_highest_perf() out of amd-pstate
x86/amd: Detect preferred cores in amd_get_boost_ratio_numerator()
cpufreq: amd-pstate: Merge amd_pstate_highest_perf_set() into
amd_get_boost_ratio_numerator()
cpufreq: amd-pstate: Optimize amd_pstate_update_limits()
cpufreq: amd-pstate: Add documentation for `amd_pstate_hw_prefcore`
amd-pstate: Add missing documentation for
`amd_pstate_prefcore_ranking`
cpufreq/amd-pstate: Export symbols for changing modes
cpufreq/amd-pstate-ut: Add test case for mode switches
Qianqiang Liu (1):
cpufreq/amd-pstate-ut: Fix an "Uninitialized variables" issue
Documentation/admin-guide/pm/amd-pstate.rst | 15 ++++++++++++++-
arch/x86/include/asm/processor.h | 3 ---
arch/x86/kernel/acpi/cppc.c | 172
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------
arch/x86/kernel/cpu/amd.c | 16 ----------------
drivers/cpufreq/acpi-cpufreq.c | 12 +++++++++---
drivers/cpufreq/amd-pstate-ut.c | 41
++++++++++++++++++++++++++++++++++++++++-
drivers/cpufreq/amd-pstate.c | 151
+++++++++++++++++++++++++++++++++++++++----------------------------------------------------------------------------------------------------------------
drivers/cpufreq/amd-pstate.h | 14 ++++++++++++++
include/acpi/cppc_acpi.h | 41
++++++++++++++++++++++++++++-------------
9 files changed, 305 insertions(+), 160 deletions(-)
next reply other threads:[~2024-09-11 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 16:01 Mario Limonciello [this message]
2024-09-11 20:13 ` second round of amd-pstate changess for 6.12 (second try) Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0f490e10-bab5-44d2-aa9f-efd80d306083@amd.com \
--to=mario.limonciello@amd.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox