From: KobaK <kobak@nvidia.com>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Fenghua Yu <fenghuay@nvidia.com>, Tushar Dave <tdave@nvidia.com>,
Kai-Heng Feng <kaihengf@nvidia.com>,
rupakr@nvidia.com, mohammedk@nvidia.com
Subject: [RFC PATCH 0/3] arm64: expose CPU prefetch and cache modulation controls
Date: Mon, 17 Aug 2026 10:23:32 +0800 [thread overview]
Message-ID: <20260817022335.3-1-kobak@nvidia.com> (raw)
From: Koba Ko <kobak@nvidia.com>
This series adds CONFIG_ARM64_CPUMOD, a default-off arm64 interface for
controlled performance characterization of selected implementation-defined
CPU prefetch and cache-management fields. It exposes a small set of named,
per-CPU attributes under the path below, with writable control fields
range-checked before register state is changed:
/sys/devices/system/cpu/cpuN/cpumod/
The directory is created for online CPUs whose MIDR matches a recognized
Grace or Vera profile, with common and profile-specific attributes selected
for that CPU. Register accesses execute on the CPU that owns the sysfs
instance, and CPU hotplug creates or removes the per-CPU subtree as the CPU
transitions online or offline. Unsupported CPU profiles are skipped without
blocking module load or CPU hotplug.
The implementation keeps each dynamically allocated kobject in a private
per-CPU pointer, avoiding use of the CPU device's shared driver-data slot.
The documentation defines the ABI, firmware prerequisite, and hotplug
lifecycle. The kselftest validates profile-specific layout, unsupported-CPU
skipping, decimal affected_cpus reporting, value validation, optional
writes, all-online-CPU coverage, and cleanup.
The controls require firmware to permit EL1 access to the relevant
implementation control registers. This is an RFC interface for controlled
evaluation, not a general raw-register or production-default tuning ABI.
Compile and static verification passed. DUT runtime validation was not run.
Koba Ko (3):
arm64: add CPU prefetch and cache modulation sysfs interface
Documentation/arch/arm64: document arm_cpumod
selftests: arm64: add arm_cpumod kselftest
Documentation/arch/arm64/arm-cpumod.rst | 89 +++
Documentation/arch/arm64/index.rst | 1 +
arch/arm64/Kconfig | 17 +
arch/arm64/kernel/Makefile | 1 +
arch/arm64/kernel/arm_cpumod.c | 471 ++++++++++++++++
arch/arm64/kernel/arm_cpumod_internal.h | 113 ++++
tools/testing/selftests/arm64/Makefile | 2 +-
.../selftests/arm64/arm_cpumod/Makefile | 5 +
.../selftests/arm64/arm_cpumod/arm_cpumod.sh | 526 ++++++++++++++++++
9 files changed, 1224 insertions(+), 1 deletion(-)
create mode 100644 Documentation/arch/arm64/arm-cpumod.rst
create mode 100644 arch/arm64/kernel/arm_cpumod.c
create mode 100644 arch/arm64/kernel/arm_cpumod_internal.h
create mode 100644 tools/testing/selftests/arm64/arm_cpumod/Makefile
create mode 100755 tools/testing/selftests/arm64/arm_cpumod/arm_cpumod.sh
--
2.43.0
next reply other threads:[~2026-08-17 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 2:23 KobaK [this message]
2026-08-17 2:23 ` [RFC PATCH 1/3] arm64: add CPU prefetch and cache modulation sysfs interface KobaK
2026-08-17 2:23 ` [RFC PATCH 2/3] Documentation/arch/arm64: document arm_cpumod KobaK
2026-08-17 2:23 ` [RFC PATCH 3/3] selftests: arm64: add arm_cpumod kselftest KobaK
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=20260817022335.3-1-kobak@nvidia.com \
--to=kobak@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=fenghuay@nvidia.com \
--cc=kaihengf@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mohammedk@nvidia.com \
--cc=rupakr@nvidia.com \
--cc=skhan@linuxfoundation.org \
--cc=tdave@nvidia.com \
--cc=will@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