From: Mark Brown <broonie@kernel.org>
To: Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Will Deacon <will@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Jonathan Corbet <corbet@lwn.net>, Shuah Khan <shuah@kernel.org>
Cc: Dave Martin <Dave.Martin@arm.com>, Fuad Tabba <tabba@google.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: [PATCH v7 28/29] KVM: arm64: selftests: Add SME system registers to get-reg-list
Date: Fri, 22 Aug 2025 02:53:57 +0100 [thread overview]
Message-ID: <20250822-kvm-arm64-sme-v7-28-7a65d82b8b10@kernel.org> (raw)
In-Reply-To: <20250822-kvm-arm64-sme-v7-0-7a65d82b8b10@kernel.org>
SME adds a number of new system registers, update get-reg-list to check for
them based on the visibility of SME.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
tools/testing/selftests/kvm/arm64/get-reg-list.c | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/kvm/arm64/get-reg-list.c b/tools/testing/selftests/kvm/arm64/get-reg-list.c
index 011fad95dd02..54b371330f57 100644
--- a/tools/testing/selftests/kvm/arm64/get-reg-list.c
+++ b/tools/testing/selftests/kvm/arm64/get-reg-list.c
@@ -61,7 +61,13 @@ static struct feature_id_reg feat_id_regs[] = {
REG_FEAT(HFGITR2_EL2, ID_AA64MMFR0_EL1, FGT, FGT2),
REG_FEAT(HDFGRTR2_EL2, ID_AA64MMFR0_EL1, FGT, FGT2),
REG_FEAT(HDFGWTR2_EL2, ID_AA64MMFR0_EL1, FGT, FGT2),
- REG_FEAT(ZCR_EL2, ID_AA64PFR0_EL1, SVE, IMP),
+ REG_FEAT(SMCR_EL1, ID_AA64PFR1_EL1, SME, IMP),
+ REG_FEAT(SMCR_EL2, ID_AA64PFR1_EL1, SME, IMP),
+ REG_FEAT(SMIDR_EL1, ID_AA64PFR1_EL1, SME, IMP),
+ REG_FEAT(SMPRI_EL1, ID_AA64PFR1_EL1, SME, IMP),
+ REG_FEAT(SMPRIMAP_EL2, ID_AA64PFR1_EL1, SME, IMP),
+ REG_FEAT(TPIDR2_EL0, ID_AA64PFR1_EL1, SME, IMP),
+ REG_FEAT(SVCR, ID_AA64PFR1_EL1, SME, IMP),
REG_FEAT(SCTLR2_EL1, ID_AA64MMFR3_EL1, SCTLRX, IMP),
REG_FEAT(VDISR_EL2, ID_AA64PFR0_EL1, RAS, IMP),
REG_FEAT(VSESR_EL2, ID_AA64PFR0_EL1, RAS, IMP),
@@ -351,6 +357,7 @@ static __u64 base_regs[] = {
ARM64_SYS_REG(3, 0, 0, 0, 0), /* MIDR_EL1 */
ARM64_SYS_REG(3, 0, 0, 0, 6), /* REVIDR_EL1 */
ARM64_SYS_REG(3, 1, 0, 0, 1), /* CLIDR_EL1 */
+ ARM64_SYS_REG(3, 1, 0, 0, 6), /* SMIDR_EL1 */
ARM64_SYS_REG(3, 1, 0, 0, 7), /* AIDR_EL1 */
ARM64_SYS_REG(3, 3, 0, 0, 1), /* CTR_EL0 */
ARM64_SYS_REG(2, 0, 0, 0, 4),
@@ -482,6 +489,8 @@ static __u64 base_regs[] = {
ARM64_SYS_REG(3, 0, 1, 0, 1), /* ACTLR_EL1 */
ARM64_SYS_REG(3, 0, 1, 0, 2), /* CPACR_EL1 */
KVM_ARM64_SYS_REG(SYS_SCTLR2_EL1),
+ ARM64_SYS_REG(3, 0, 1, 2, 4), /* SMPRI_EL1 */
+ ARM64_SYS_REG(3, 0, 1, 2, 6), /* SMCR_EL1 */
ARM64_SYS_REG(3, 0, 2, 0, 0), /* TTBR0_EL1 */
ARM64_SYS_REG(3, 0, 2, 0, 1), /* TTBR1_EL1 */
ARM64_SYS_REG(3, 0, 2, 0, 2), /* TCR_EL1 */
@@ -502,9 +511,11 @@ static __u64 base_regs[] = {
ARM64_SYS_REG(3, 0, 13, 0, 4), /* TPIDR_EL1 */
ARM64_SYS_REG(3, 0, 14, 1, 0), /* CNTKCTL_EL1 */
ARM64_SYS_REG(3, 2, 0, 0, 0), /* CSSELR_EL1 */
+ ARM64_SYS_REG(3, 3, 4, 2, 2), /* SVCR */
ARM64_SYS_REG(3, 3, 10, 2, 4), /* POR_EL0 */
ARM64_SYS_REG(3, 3, 13, 0, 2), /* TPIDR_EL0 */
ARM64_SYS_REG(3, 3, 13, 0, 3), /* TPIDRRO_EL0 */
+ ARM64_SYS_REG(3, 3, 13, 0, 5), /* TPIDR2_EL0 */
ARM64_SYS_REG(3, 3, 14, 0, 1), /* CNTPCT_EL0 */
ARM64_SYS_REG(3, 3, 14, 2, 1), /* CNTP_CTL_EL0 */
ARM64_SYS_REG(3, 3, 14, 2, 2), /* CNTP_CVAL_EL0 */
@@ -713,6 +724,8 @@ static __u64 el2_regs[] = {
SYS_REG(HFGITR_EL2),
SYS_REG(HACR_EL2),
SYS_REG(ZCR_EL2),
+ SYS_REG(SMPRIMAP_EL2),
+ SYS_REG(SMCR_EL2),
SYS_REG(HCRX_EL2),
SYS_REG(TTBR0_EL2),
SYS_REG(TTBR1_EL2),
--
2.39.5
next prev parent reply other threads:[~2025-08-22 1:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 1:53 [PATCH v7 00/29] KVM: arm64: Implement support for SME Mark Brown
2025-08-22 1:53 ` [PATCH v7 01/29] arm64/sysreg: Update SMIDR_EL1 to DDI0601 2025-06 Mark Brown
2025-08-22 1:53 ` [PATCH v7 02/29] arm64/fpsimd: Update FA64 and ZT0 enables when loading SME state Mark Brown
2025-08-22 1:53 ` [PATCH v7 03/29] arm64/fpsimd: Decide to save ZT0 and streaming mode FFR at bind time Mark Brown
2025-08-22 1:53 ` [PATCH v7 04/29] arm64/fpsimd: Check enable bit for FA64 when saving EFI state Mark Brown
2025-08-22 1:53 ` [PATCH v7 05/29] arm64/fpsimd: Determine maximum virtualisable SME vector length Mark Brown
2025-08-22 1:53 ` [PATCH v7 06/29] KVM: arm64: Introduce non-UNDEF FGT control Mark Brown
2025-08-22 1:53 ` [PATCH v7 07/29] KVM: arm64: Pay attention to FFR parameter in SVE save and load Mark Brown
2025-08-22 1:53 ` [PATCH v7 08/29] KVM: arm64: Pull ctxt_has_ helpers to start of sysreg-sr.h Mark Brown
2025-08-22 1:53 ` [PATCH v7 09/29] KVM: arm64: Move SVE state access macros after feature test macros Mark Brown
2025-08-22 1:53 ` [PATCH v7 10/29] KVM: arm64: Rename SVE finalization constants to be more general Mark Brown
2025-08-22 1:53 ` [PATCH v7 11/29] KVM: arm64: Document the KVM ABI for SME Mark Brown
2025-08-22 6:50 ` Randy Dunlap
2025-08-22 1:53 ` [PATCH v7 12/29] KVM: arm64: Define internal features " Mark Brown
2025-08-22 1:53 ` [PATCH v7 13/29] KVM: arm64: Rename sve_state_reg_region Mark Brown
2025-08-22 1:53 ` [PATCH v7 14/29] KVM: arm64: Store vector lengths in an array Mark Brown
2025-08-22 1:53 ` [PATCH v7 15/29] KVM: arm64: Implement SME vector length configuration Mark Brown
2025-08-22 1:53 ` [PATCH v7 16/29] KVM: arm64: Support SME control registers Mark Brown
2025-08-22 1:53 ` [PATCH v7 17/29] KVM: arm64: Support TPIDR2_EL0 Mark Brown
2025-08-22 1:53 ` [PATCH v7 18/29] KVM: arm64: Support SME identification registers for guests Mark Brown
2025-08-22 1:53 ` [PATCH v7 19/29] KVM: arm64: Support SME priority registers Mark Brown
2025-08-22 1:53 ` [PATCH v7 20/29] KVM: arm64: Provide assembly for SME register access Mark Brown
2025-08-22 1:53 ` [PATCH v7 21/29] KVM: arm64: Support userspace access to streaming mode Z and P registers Mark Brown
2025-08-22 1:53 ` [PATCH v7 22/29] KVM: arm64: Flush register state on writes to SVCR.SM and SVCR.ZA Mark Brown
2025-08-22 1:53 ` [PATCH v7 23/29] KVM: arm64: Expose SME specific state to userspace Mark Brown
2025-08-22 1:53 ` [PATCH v7 24/29] KVM: arm64: Context switch SME state for guests Mark Brown
2025-08-22 1:53 ` [PATCH v7 25/29] KVM: arm64: Handle SME exceptions Mark Brown
2025-08-22 1:53 ` [PATCH v7 26/29] KVM: arm64: Expose SME to nested guests Mark Brown
2025-08-22 1:53 ` [PATCH v7 27/29] KVM: arm64: Provide interface for configuring and enabling SME for guests Mark Brown
2025-08-22 1:53 ` Mark Brown [this message]
2025-08-22 1:53 ` [PATCH v7 29/29] KVM: arm64: selftests: Add SME to set_id_regs test Mark Brown
2025-09-01 12:44 ` [PATCH v7 00/29] KVM: arm64: Implement support for SME Marc Zyngier
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=20250822-kvm-arm64-sme-v7-28-7a65d82b8b10@kernel.org \
--to=broonie@kernel.org \
--cc=Dave.Martin@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--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=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.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;
as well as URLs for NNTP newsgroup(s).