From: "Mario Limonciello (AMD)" <superm1@kernel.org>
To: "Rafael J . Wysocki ⏎" <rafael@kernel.org>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org,
K Prateek Nayak <kprateek.nayak@amd.com>,
x86@kernel.org, Mario Limonciello <superm1@kernel.org>
Subject: [PATCH 0/6] Add CPPC HighestFreq support
Date: Sun, 26 Apr 2026 22:55:14 -0500 [thread overview]
Message-ID: <20260427035520.1427080-1-superm1@kernel.org> (raw)
On some systems, the boost ratio cannot be accurately calculated
using linear interpolation of CPPC performance values because the
performance-to-frequency mapping is not linear across all cores.
This series introduces support for the CPPC HighestFreq register. This
register is under a proposal with ASWG at the moment and trending for
inclusion in ACPI 6.7.
This optionally provides the actual highest frequency eliminating
the need for interpolation. When available, this frequency value is used
for more accurate CPU capacity calculations and boost ratio determination.
This series brings the existing CPPC definitions up to ACPI 6.6 and then
adds support for the ACPI 6.7 proposal.
Mario Limonciello (6):
Revert "ACPI: CPPC: Adjust debug messages in amd_set_max_freq_ratio()
to warn"
ACPI: Add CPPC v4 definitions
ACPI: CPPC: Add support for reading HighestFreq
ACPI: CPPC: Refactor boost ratio handling
cpufreq/acpi-cpufreq: Use amd_get_boost_ratio()
cpufreq/amd-pstate: Get highest freq from CPPC if available
arch/x86/kernel/acpi/cppc.c | 122 ++++++++++++++++++---------------
drivers/acpi/cppc_acpi.c | 39 ++++++++---
drivers/cpufreq/acpi-cpufreq.c | 17 +++--
drivers/cpufreq/amd-pstate.c | 18 +++--
include/acpi/cppc_acpi.h | 27 ++++++--
5 files changed, 139 insertions(+), 84 deletions(-)
--
2.43.0
next reply other threads:[~2026-04-27 3:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 3:55 Mario Limonciello (AMD) [this message]
2026-04-27 3:55 ` [PATCH 1/6] Revert "ACPI: CPPC: Adjust debug messages in amd_set_max_freq_ratio() to warn" Mario Limonciello (AMD)
2026-04-27 3:55 ` [PATCH 2/6] ACPI: Add CPPC v4 definitions Mario Limonciello (AMD)
2026-04-27 3:55 ` [PATCH 3/6] ACPI: CPPC: Add support for reading HighestFreq Mario Limonciello (AMD)
2026-04-27 3:55 ` [PATCH 4/6] ACPI: CPPC: Refactor boost ratio handling Mario Limonciello (AMD)
2026-04-27 3:55 ` [PATCH 5/6] cpufreq/acpi-cpufreq: Use amd_get_boost_ratio() Mario Limonciello (AMD)
2026-04-27 3:55 ` [PATCH 6/6] cpufreq/amd-pstate: Get highest freq from CPPC if available Mario Limonciello (AMD)
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=20260427035520.1427080-1-superm1@kernel.org \
--to=superm1@kernel.org \
--cc=kprateek.nayak@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=x86@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