From: K Prateek Nayak <kprateek.nayak@amd.com>
To: "Mario Limonciello (AMD)" <superm1@kernel.org>,
"Rafael J . Wysocki ⏎" <rafael@kernel.org>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-pm@vger.kernel.org>, <x86@kernel.org>
Subject: Re: [PATCH v3 0/3] Zen6 client CPPC
Date: Thu, 1 Oct 2026 21:07:28 +0530 [thread overview]
Message-ID: <9c65d1b2-4c9e-44a4-82ea-4351ff9aa6b2@amd.com> (raw)
In-Reply-To: <20260924160052.2858456-1-superm1@kernel.org>
Hello Mario,
On 9/24/2026 9:30 PM, Mario Limonciello (AMD) wrote:
> From: Mario Limonciello <superm1@kernel.org>
>
> Zen6 client platforms use CPPC differently than previous platforms
> and knowing maximum frequency for a core type is needed for capacity
> calculations.
>
> Newer versions of the ACPI will introduce a proper interface
> for getting this information, but for now hardcode values so that
> these systems perform as intended and to unblock future scheduler
> work while we continue to wait.
For the whole series, feel free to include:
Reviewed-by: K Prateek Nayak <kprateek.nayak@amd.com>
Tested-by: K Prateek Nayak <kprateek.nayak@amd.com>
FWIW, I've been running bleeding-edge branch for a bunch of
tests today and everything looks fine.
--
Thanks and Regards,
Prateek
prev parent reply other threads:[~2026-10-01 15:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 16:00 Mario Limonciello (AMD)
2026-09-24 16:00 ` [PATCH v3 1/3] ACPI: CPPC: Refactor boost ratio handling Mario Limonciello (AMD)
2026-09-25 9:40 ` Christian Loehle
2026-09-25 14:54 ` Mario Limonciello
2026-09-30 19:37 ` Rafael J. Wysocki (Intel)
2026-09-30 19:41 ` Mario Limonciello
2026-09-30 19:43 ` Rafael J. Wysocki (Intel)
2026-09-30 19:45 ` Mario Limonciello
2026-09-24 16:00 ` [PATCH v3 2/3] cpufreq/acpi-cpufreq: Use amd_get_boost_ratio() Mario Limonciello (AMD)
2026-09-24 16:00 ` [PATCH v3 3/3] cpufreq/amd-pstate: Get Highest Freq for a CPU Mario Limonciello (AMD)
2026-10-01 10:03 ` Christian Loehle
2026-10-01 13:47 ` Mario Limonciello
2026-10-01 15:37 ` K Prateek Nayak [this message]
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=9c65d1b2-4c9e-44a4-82ea-4351ff9aa6b2@amd.com \
--to=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=superm1@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
all inboxes | Powered by JetHome®