From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.linux.dev, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Volodymyr Babchuk <volodymyr_babchuk@epam.com>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: [PATCH 0/2] KVM: arm64: AT + SR accessor fixes
Date: Sat, 9 Aug 2025 15:48:09 +0100 [thread overview]
Message-ID: <20250809144811.2314038-1-maz@kernel.org> (raw)
Volodymyr having reported[1] a couple of rather interesting bugs while
running Xen under KVM, here's a couple of patches to plug these
issues:
- a fix for ATS12 stopping the walk at S1 under the wrong conditions
- a much larger fix for the vcpu_{read,write}_sys_reg() accessors,
fixing the fate of TPIDR*_EL{0,1} and PAR_EL1, and overall becoming
much easier to work with
The latter is a pretty large change, but is worth it IMO as it makes
everything much more straightforward.
Volodymyr, I'd very much welcome your feedback on those, as despite my
best effort, I didn't manage to even boot Debian's packaging of Xen
(Grub just refuses to run *anything* after Xen being installed -- I
guess it's not tested at all).
[1] https://lore.kernel.org/r/20250806141707.3479194-1-volodymyr_babchuk@epam.com
Marc Zyngier (2):
KVM: arm64: nv: Fix ATS12 handling of single-stage translation
KVM: arm64: Fix vcpu_{read,write}_sys_reg() accessors
arch/arm64/include/asm/kvm_host.h | 4 +-
arch/arm64/kvm/at.c | 6 +-
arch/arm64/kvm/sys_regs.c | 243 +++++++++++++++---------------
3 files changed, 130 insertions(+), 123 deletions(-)
--
2.39.2
next reply other threads:[~2025-08-09 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 14:48 Marc Zyngier [this message]
2025-08-09 14:48 ` [PATCH 1/2] KVM: arm64: nv: Fix ATS12 handling of single-stage translation Marc Zyngier
2025-08-09 14:48 ` [PATCH 2/2] KVM: arm64: Fix vcpu_{read,write}_sys_reg() accessors Marc Zyngier
2025-08-12 20:23 ` Oliver Upton
2025-08-13 6:54 ` Marc Zyngier
2025-08-14 16:16 ` Marc Zyngier
2025-08-15 18:56 ` 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=20250809144811.2314038-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=volodymyr_babchuk@epam.com \
--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;
as well as URLs for NNTP newsgroup(s).