From: Mark Brown <broonie@kernel.org>
To: Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@kernel.org>,
Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Fuad Tabba <fuad.tabba@linux.dev>
Cc: Peter Maydell <peter.maydell@linaro.org>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Fuad Tabba <fuad.tabba@linux.dev>,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Subject: [PATCH v4 0/3] KVM: arm64: ID register finalisation fixes
Date: Tue, 29 Sep 2026 12:57:57 +0100 [thread overview]
Message-ID: <20260929-kvm-arm64-idreg-final-v4-0-75296dde994d@kernel.org> (raw)
While looking at some feature enablement I noticed that there are some
scenarios where we can end up with an inconsistently configured vCPU due
to finalizing configuration based on ID registers before we have blocked
writes to the ID registers. This series aims to clean up these issues.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
Changes in v4:
- Rebase onto v7.3-rc3.
- Add a lockdep assert.
- Update Fuad's LLM tag.
- Link to v3: https://patch.msgid.link/20260901-kvm-arm64-idreg-final-v3-0-a0ffa06fa872@kernel.org
Changes in v3:
- Rebase onto v7.3-rc1.
- Explain why KVM_ARCH_FLAG_ID_REGS_INITIALIZED is not reused.
- Pull in Fuad's test cases.
- Link to v2: https://patch.msgid.link/20260803-kvm-arm64-idreg-final-v2-0-d7d7e4efc640@kernel.org
Changes in v2:
- Also replace the kvm_vm_has_ran_once() usage in kvm_set_vm_id_rg() and
kvm_vm_finalize_sys_regs() with kvm_id_regs_final().
- Link to v1: https://patch.msgid.link/20260731-kvm-arm64-idreg-final-v1-0-3de2a5616dc6@kernel.org
---
Fuad Tabba (1):
KVM: arm64: selftests: Check ID regs are immutable after a failed run
Mark Brown (2):
KVM: arm64: Finalize guest-wide sysregs prior to per-vCPU sysregs
KVM: arm64: Block ID register changes after we rely on the values
arch/arm64/include/asm/kvm_host.h | 8 ++
arch/arm64/kvm/arm.c | 2 +-
arch/arm64/kvm/sys_regs.c | 57 ++++++++-----
arch/arm64/kvm/sys_regs.h | 2 +-
arch/arm64/kvm/vgic/vgic-init.c | 6 +-
tools/testing/selftests/kvm/arm64/set_id_regs.c | 106 +++++++++++++++++++++++-
6 files changed, 154 insertions(+), 27 deletions(-)
---
base-commit: fd73f4a6659897191fa0d40695fe370925dd3780
change-id: 20260729-kvm-arm64-idreg-final-77cbc46b558a
Best regards,
--
Mark Brown <broonie@kernel.org>
next reply other threads:[~2026-09-29 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 11:57 Mark Brown [this message]
2026-09-29 11:57 ` [PATCH v4 1/3] KVM: arm64: Finalize guest-wide sysregs prior to per-vCPU sysregs Mark Brown
2026-09-29 11:57 ` [PATCH v4 2/3] KVM: arm64: Block ID register changes after we rely on the values Mark Brown
2026-09-29 11:58 ` [PATCH v4 3/3] KVM: arm64: selftests: Check ID regs are immutable after a failed run Mark Brown
2026-09-29 23:02 ` [PATCH v4 0/3] KVM: arm64: ID register finalisation fixes Oliver Upton
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=20260929-kvm-arm64-idreg-final-v4-0-75296dde994d@kernel.org \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=peter.maydell@linaro.org \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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®