From: Mario Limonciello <superm1@kernel.org>
To: Borislav Petkov <bp@alien8.de>, "Rafael J . Wysocki" <rafael@kernel.org>
Cc: x86@kernel.org, linux-acpi@vger.kernel.org,
Perry Yuan <perry.yuan@amd.com>,
gautham.shenoy@amd.com,
Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH 0/2] Detect max performance values for heterogeneous AMD designs
Date: Thu, 3 Oct 2024 16:37:57 -0500 [thread overview]
Message-ID: <20241003213759.3038862-1-superm1@kernel.org> (raw)
From: Mario Limonciello <mario.limonciello@amd.com>
AMD heterogeneous designs such as the Ryzen AI 300 series processors have
multiple core types that can reach different maximum clock values.
This series uses the CPUID Fn_0x80000026 to detect such designs and to
correct configure the boost numerator that is used to calculate maximum
frequency.
Mario Limonciello (1):
CPPC: Use heterogeneous core topology for identifying boost numerator
Perry Yuan (1):
x86/cpufeatures: Add feature bits for AMD heterogeneous processor
arch/x86/include/asm/cpufeatures.h | 1 +
arch/x86/include/asm/processor.h | 13 +++++++++++++
arch/x86/kernel/acpi/cppc.c | 30 ++++++++++++++++++++++++++++++
arch/x86/kernel/cpu/amd.c | 29 +++++++++++++++++++++++++++++
arch/x86/kernel/cpu/scattered.c | 1 +
5 files changed, 74 insertions(+)
--
2.43.0
next reply other threads:[~2024-10-03 21:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 21:37 Mario Limonciello [this message]
2024-10-03 21:37 ` [PATCH 1/2] x86/cpufeatures: Add feature bits for AMD heterogeneous processor Mario Limonciello
2024-10-04 4:06 ` Gautham R. Shenoy
2024-10-18 18:24 ` Borislav Petkov
2024-10-18 18:31 ` Mario Limonciello
2024-10-19 10:10 ` Borislav Petkov
2024-10-21 10:32 ` Rafael J. Wysocki
2024-10-21 10:49 ` Borislav Petkov
2024-10-03 21:37 ` [PATCH 2/2] CPPC: Use heterogeneous core topology for identifying boost numerator Mario Limonciello
2024-10-04 4:14 ` Gautham R. Shenoy
2024-10-21 10:58 ` Borislav Petkov
2024-10-21 17:52 ` Mario Limonciello
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=20241003213759.3038862-1-superm1@kernel.org \
--to=superm1@kernel.org \
--cc=bp@alien8.de \
--cc=gautham.shenoy@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perry.yuan@amd.com \
--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