From: Vishal Badole <Vishal.Badole@amd.com>
To: <ray.huang@amd.com>, <mario.limonciello@amd.com>,
<rafael@kernel.org>, <viresh.kumar@linaro.org>,
<perry.yuan@amd.com>, <kprateek.nayak@amd.com>,
<hansg@kernel.org>, <ilpo.jarvinen@linux.intel.com>,
<platform-driver-x86@vger.kernel.org>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Vishal Badole <Vishal.Badole@amd.com>
Subject: [PATCH 0/2] cpufreq: amd-pstate: Capacity Aware Scheduling on hybrid platforms
Date: Sat, 14 Nov 2026 20:33:08 +0530 [thread overview]
Message-ID: <20261114150310.1377654-1-Vishal.Badole@amd.com> (raw)
This series enables Capacity Aware Scheduling (CAS) for AMD heterogeneous
processors that combine performance and efficiency cores.
amd-pstate does not export per-CPU capacity today, so the scheduler treats
all cores as equal and places tasks without regard to core strength.
Patch 1 makes amd-pstate publish asymmetric per-CPU capacities via the arch
hybrid capacity scaling interface. It is enabled by default on supported
hardware and can be turned off with the "amd_cas=disable" boot parameter.
Patch 2 makes amd-hfi stand down when CAS is active, since both manage the
same scheduler state.
Krishnamoorthi M (1):
platform/x86/amd: hfi: Stand down when amd-pstate CAS is active
Vishal Badole (1):
cpufreq: amd-pstate: Set asymmetric CPU capacity on hybrid platforms
MAINTAINERS | 1 +
drivers/cpufreq/amd-pstate.c | 102 ++++++++++++++++++++++++++++-
drivers/platform/x86/amd/hfi/hfi.c | 8 +++
include/linux/amd-pstate.h | 14 ++++
4 files changed, 123 insertions(+), 2 deletions(-)
create mode 100644 include/linux/amd-pstate.h
--
2.34.1
next reply other threads:[~2026-11-14 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-14 15:03 Vishal Badole [this message]
2026-11-14 15:03 ` [PATCH 1/2] cpufreq: amd-pstate: Set asymmetric CPU capacity " Vishal Badole
2026-11-14 15:03 ` [PATCH 2/2] platform/x86/amd: hfi: Stand down when amd-pstate CAS is active Vishal Badole
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=20261114150310.1377654-1-Vishal.Badole@amd.com \
--to=vishal.badole@amd.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perry.yuan@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.com \
--cc=viresh.kumar@linaro.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®