From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Jonathan Corbet <corbet@lwn.net>, Shuah Khan <shuah@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
Mark Brown <broonie@kernel.org>
Subject: [PATCH 14/21] KVM: arm64: Add newly allocated ID registers to register descriptions
Date: Thu, 26 Oct 2023 13:44:28 +0100 [thread overview]
Message-ID: <20231026-arm64-2023-dpisa-v1-14-8470dd989bb2@kernel.org> (raw)
In-Reply-To: <20231026-arm64-2023-dpisa-v1-0-8470dd989bb2@kernel.org>
The 2023 architecture extensions have allocated some new ID registers, add
them to the KVM system register descriptions so that they are visible to
guests.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
arch/arm64/kvm/sys_regs.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c
index 0afd6136e275..99cdaa594b06 100644
--- a/arch/arm64/kvm/sys_regs.c
+++ b/arch/arm64/kvm/sys_regs.c
@@ -2016,12 +2016,12 @@ static const struct sys_reg_desc sys_reg_descs[] = {
.reset = read_sanitised_id_aa64pfr0_el1,
.val = ID_AA64PFR0_EL1_CSV2_MASK | ID_AA64PFR0_EL1_CSV3_MASK, },
ID_SANITISED(ID_AA64PFR1_EL1),
- ID_UNALLOCATED(4,2),
+ ID_SANITISED(ID_AA64PFR2_EL1),
ID_UNALLOCATED(4,3),
ID_SANITISED(ID_AA64ZFR0_EL1),
ID_HIDDEN(ID_AA64SMFR0_EL1),
ID_UNALLOCATED(4,6),
- ID_UNALLOCATED(4,7),
+ ID_SANITISED(ID_AA64FPFR0_EL1),
/* CRm=5 */
{ SYS_DESC(SYS_ID_AA64DFR0_EL1),
@@ -2042,7 +2042,7 @@ static const struct sys_reg_desc sys_reg_descs[] = {
ID_SANITISED(ID_AA64ISAR0_EL1),
ID_SANITISED(ID_AA64ISAR1_EL1),
ID_SANITISED(ID_AA64ISAR2_EL1),
- ID_UNALLOCATED(6,3),
+ ID_SANITISED(ID_AA64ISAR3_EL1),
ID_UNALLOCATED(6,4),
ID_UNALLOCATED(6,5),
ID_UNALLOCATED(6,6),
--
2.30.2
next prev parent reply other threads:[~2023-10-26 12:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 12:44 [PATCH 00/21] arm64: Support for 2023 DPISA extensions Mark Brown
2023-10-26 12:44 ` [PATCH 01/21] arm64/sysreg: Add definition for ID_AA64PFR2_EL1 Mark Brown
2023-10-26 12:44 ` [PATCH 02/21] arm64/sysreg: Update ID_AA64ISAR2_EL1 defintion for DDI0601 2023-09 Mark Brown
2023-10-26 12:44 ` [PATCH 03/21] arm64/sysreg: Add definition for ID_AA64ISAR3_EL1 Mark Brown
2023-10-26 12:44 ` [PATCH 04/21] arm64/sysreg: Add definition for ID_AA64FPFR0_EL1 Mark Brown
2023-10-26 12:44 ` [PATCH 05/21] arm64/sysreg: Update ID_AA64SMFR0_EL1 definition for DDI0601 2023-09 Mark Brown
2023-10-26 12:44 ` [PATCH 06/21] arm64/sysreg: Update SCTLR_EL1 " Mark Brown
2023-10-26 12:44 ` [PATCH 07/21] arm64/sysreg: Update HCRX_EL2 definition " Mark Brown
2023-10-26 12:44 ` [PATCH 08/21] arm64/sysreg: Add definition for FPMR Mark Brown
2023-10-26 12:44 ` [PATCH 09/21] arm64/cpufeature: Hook new identification registers up to cpufeature Mark Brown
2023-10-26 12:44 ` [PATCH 10/21] arm64/fpsimd: Enable host kernel access to FPMR Mark Brown
2023-10-26 12:44 ` [PATCH 11/21] arm64/fpsimd: Support FEAT_FPMR Mark Brown
2023-10-26 12:44 ` [PATCH 12/21] arm64/signal: Add FPMR signal handling Mark Brown
2023-10-26 12:44 ` [PATCH 13/21] arm64/ptrace: Expose FPMR via ptrace Mark Brown
2023-10-26 12:44 ` Mark Brown [this message]
2023-10-26 12:44 ` [PATCH 15/21] KVM: arm64: Support FEAT_FPMR for guests Mark Brown
2023-10-26 12:44 ` [PATCH 16/21] arm64/hwcap: Define hwcaps for 2023 DPISA features Mark Brown
2023-10-26 12:44 ` [PATCH 17/21] kselftest/arm64: Handle FPMR context in generic signal frame parser Mark Brown
2023-10-26 12:44 ` [PATCH 18/21] kselftest/arm64: Add basic FPMR test Mark Brown
2023-10-26 12:44 ` [PATCH 19/21] kselftest/arm64: Add 2023 DPISA hwcap test coverage Mark Brown
2023-10-26 12:44 ` [PATCH 20/21] KVM: arm64: selftests: Document feature registers added in 2023 extensions Mark Brown
2023-10-26 12:44 ` [PATCH 21/21] KVM: arm64: selftests: Teach get-reg-list about FPMR Mark Brown
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=20231026-arm64-2023-dpisa-v1-14-8470dd989bb2@kernel.org \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=james.morse@arm.com \
--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=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.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
all inboxes | Powered by JetHome®