From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Cc: 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 v2 0/4] KVM: arm64: vcpu sysreg accessor rework
Date: Tue, 3 Jun 2025 08:08:20 +0100 [thread overview]
Message-ID: <20250603070824.1192795-1-maz@kernel.org> (raw)
This series tries to bring some sanity to the way the RESx masks
are applied when accessing the in-memory view of the guest's
system registers.
Currently, we have *one* accessor (__vcpu_sys_reg()) that can either
be used as a rvalue or lvalue while that applies the RESx masks behind
the scenes. This works fine when used as a rvalue.
However, when used as a lvalue, it does the wrong thing, as it only
sanitises the value we're about to overwrite. This is pointless work
and potentially hides bugs.
I propose that we move to a set of store-specific accessors (for
assignments and RMW) instead of the lvalue hack, ensuring that the
assigned value is the one that gets sanitised. This then allows the
legacy accessor to be converted to rvalue-only.
Given the level of churn this introduces, I'd like this to land very
early in the cycle. Either before 6.16-rc2, or early in 6.17.
* From v1 [1]
- rebased to kvmarm-fixes-6.16-1
[1] https://lore.kernel.org/all/20250113183524.1378778-1-maz@kernel.org/
Marc Zyngier (4):
KVM: arm64: Add assignment-specific sysreg accessor
KVM: arm64: Add RMW specific sysreg accessor
KVM: arm64: Don't use __vcpu_sys_reg() to get the address of a sysreg
KVM: arm64: Make __vcpu_sys_reg() a pure rvalue operand
arch/arm64/include/asm/kvm_host.h | 31 +++++++++--
arch/arm64/kvm/arch_timer.c | 18 +++----
arch/arm64/kvm/debug.c | 4 +-
arch/arm64/kvm/fpsimd.c | 4 +-
arch/arm64/kvm/hyp/exception.c | 4 +-
arch/arm64/kvm/hyp/include/hyp/switch.h | 4 +-
arch/arm64/kvm/hyp/include/hyp/sysreg-sr.h | 6 +--
arch/arm64/kvm/hyp/nvhe/hyp-main.c | 4 +-
arch/arm64/kvm/hyp/vhe/switch.c | 4 +-
arch/arm64/kvm/hyp/vhe/sysreg-sr.c | 48 ++++++++---------
arch/arm64/kvm/nested.c | 2 +-
arch/arm64/kvm/pmu-emul.c | 24 ++++-----
arch/arm64/kvm/sys_regs.c | 60 +++++++++++-----------
arch/arm64/kvm/sys_regs.h | 4 +-
arch/arm64/kvm/vgic/vgic-v3-nested.c | 10 ++--
15 files changed, 125 insertions(+), 102 deletions(-)
--
2.39.2
next reply other threads:[~2025-06-03 7:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 7:08 Marc Zyngier [this message]
2025-06-03 7:08 ` [PATCH v2 1/4] KVM: arm64: Add assignment-specific sysreg accessor Marc Zyngier
2025-06-03 18:01 ` Miguel Luis
2025-06-04 6:52 ` Marc Zyngier
2025-06-04 10:14 ` Miguel Luis
2025-06-03 7:08 ` [PATCH v2 2/4] KVM: arm64: Add RMW specific " Marc Zyngier
2025-06-03 7:08 ` [PATCH v2 3/4] KVM: arm64: Don't use __vcpu_sys_reg() to get the address of a sysreg Marc Zyngier
2025-06-03 7:08 ` [PATCH v2 4/4] KVM: arm64: Make __vcpu_sys_reg() a pure rvalue operand Marc Zyngier
2025-06-03 21:06 ` [PATCH v2 0/4] KVM: arm64: vcpu sysreg accessor rework Oliver Upton
2025-06-04 6:54 ` Marc Zyngier
2025-06-04 10:47 ` Miguel Luis
2025-06-04 15:17 ` Marc Zyngier
2025-06-04 15:53 ` Miguel Luis
2025-06-04 18:58 ` Marc Zyngier
2025-06-05 9:40 ` Miguel Luis
2025-06-05 13:34 ` 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=20250603070824.1192795-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.