Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	kvm@vger.kernel.org
Cc: Steffen Eiden <seiden@linux.ibm.com>,
	Joey Gouly <joey.gouly@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Oliver Upton <oupton@kernel.org>,
	Zenghui Yu <yuzenghui@huawei.com>
Subject: [PATCH v2 16/28] KVM: arm64: Split NV-specific exit fixups from the non-NV handling
Date: Tue, 14 Jul 2026 10:16:29 +0100	[thread overview]
Message-ID: <20260714091641.1970822-17-maz@kernel.org> (raw)
In-Reply-To: <20260714091641.1970822-1-maz@kernel.org>

In order to facilitate further changes, move the NV handling of
early fixups in its own helper. This also makes the code slightly
simpler to parse.

Signed-off-by: Marc Zyngier <maz@kernel.org>
---
 arch/arm64/kvm/hyp/vhe/switch.c | 18 +++++++++++-------
 1 file changed, 11 insertions(+), 7 deletions(-)

diff --git a/arch/arm64/kvm/hyp/vhe/switch.c b/arch/arm64/kvm/hyp/vhe/switch.c
index 8460a8a6745b3..e26cc575e60e1 100644
--- a/arch/arm64/kvm/hyp/vhe/switch.c
+++ b/arch/arm64/kvm/hyp/vhe/switch.c
@@ -534,18 +534,15 @@ static const exit_handler_fn hyp_exit_handlers[] = {
 	[0x3F]				= kvm_hyp_handle_impdef,
 };
 
-static inline bool fixup_guest_exit(struct kvm_vcpu *vcpu, u64 *exit_code)
+static void fixup_nv_guest_exit(struct kvm_vcpu *vcpu)
 {
-	synchronize_vcpu_pstate(vcpu);
-
 	/*
 	 * If we were in HYP context on entry, adjust the PSTATE view
 	 * so that the usual helpers work correctly. This enforces our
 	 * invariant that the guest's HYP context status is preserved
 	 * across a run.
 	 */
-	if (vcpu_has_nv(vcpu) &&
-	    unlikely(host_data_test_flag(VCPU_IN_HYP_CONTEXT))) {
+	if (unlikely(host_data_test_flag(VCPU_IN_HYP_CONTEXT))) {
 		u64 mode = *vcpu_cpsr(vcpu) & (PSR_MODE_MASK | PSR_MODE32_BIT);
 
 		switch (mode) {
@@ -562,8 +559,15 @@ static inline bool fixup_guest_exit(struct kvm_vcpu *vcpu, u64 *exit_code)
 	}
 
 	/* Apply extreme paranoia! */
-	BUG_ON(vcpu_has_nv(vcpu) &&
-	       !!host_data_test_flag(VCPU_IN_HYP_CONTEXT) != is_hyp_ctxt(vcpu));
+	BUG_ON(!!host_data_test_flag(VCPU_IN_HYP_CONTEXT) != is_hyp_ctxt(vcpu));
+}
+
+static bool fixup_guest_exit(struct kvm_vcpu *vcpu, u64 *exit_code)
+{
+	synchronize_vcpu_pstate(vcpu);
+
+	if (vcpu_has_nv(vcpu))
+		fixup_nv_guest_exit(vcpu);
 
 	return __fixup_guest_exit(vcpu, exit_code, hyp_exit_handlers);
 }
-- 
2.47.3


  parent reply	other threads:[~2026-07-14  9:16 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  9:16 [PATCH v2 00/28] KVM: arm64: Add support for FEAT_NV2p1 and FEAT_NV3 Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 01/28] arm64: sysreg: Emit RESx/UNKN values for Mapping/Fields definitions Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 02/28] arm64: Update ID_AA64MMFR4_EL1 description to 2026-03 JSON release Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 03/28] KVM: arm64: Merge guest's HCRX_EL2 using NV_HCRX_GUEST_EXCLUDE Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 04/28] KVM: arm64: Drop __HCRX_EL2_* masks Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 05/28] KVM: arm64: Plumb HCRX_EL2.SRMASKEn in HCRX_EL2 sanitisation Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 06/28] KVM: arm64: Classify CPTR_EL2 as a SR_LOC_SPECIAL register Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 07/28] KVM: arm64: Don't evaluate HCR_EL2.NV nor HFGITR_EL2.ERET on ERET fast path Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 08/28] arm64: Add ARM64_HAS_NV2P1 capability Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 09/28] KVM: arm64: Relax CPTR_EL2 handling when FEAT_NV2p1 is present Marc Zyngier
2026-07-14 10:12   ` sashiko-bot
2026-07-14  9:16 ` [PATCH v2 10/28] KVM: arm64: Relax CNTHCTL_EL2 " Marc Zyngier
2026-07-14  9:53   ` sashiko-bot
2026-07-14  9:16 ` [PATCH v2 11/28] KVM: arm64: Expose FEAT_NV2p1 to NV guests Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 12/28] arm64: Add FEAT_NV2p1 detection Marc Zyngier
2026-07-14  9:46   ` sashiko-bot
2026-07-14 11:45     ` Marc Zyngier
2026-07-14 13:18       ` Fuad Tabba
2026-07-14  9:16 ` [PATCH v2 13/28] arm64: sysreg: Add NVHCR_EL2 description as a mirror of HCR_EL2 Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 14/28] arm64: sysreg: Add HCRX_EL2 bits related to FEAT_NV3 Marc Zyngier
2026-07-14  9:45   ` sashiko-bot
2026-07-14 13:04     ` Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 15/28] arm64: Add ARM64_HAS_NV3 capability Marc Zyngier
2026-07-14  9:40   ` sashiko-bot
2026-07-14 11:42     ` Marc Zyngier
2026-07-14  9:16 ` Marc Zyngier [this message]
2026-07-14  9:16 ` [PATCH v2 17/28] KVM: arm64: Add NV3 control bits to HCRX_EL2 sanitisation Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 18/28] KVM: arm64: Add kvm_has_nv{2,3}() predicates Marc Zyngier
2026-07-14  9:48   ` sashiko-bot
2026-07-14  9:16 ` [PATCH v2 19/28] KVM: arm64: Make HCR_EL2 a non-VNCR register Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 20/28] KVM: arm64: Add sanitisation for NVHCR_EL2 Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 21/28] KVM: arm64: Add NVHCR_EL2 handling to the sysreg array Marc Zyngier
2026-07-14 10:24   ` sashiko-bot
2026-07-14 12:56     ` Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 22/28] KVM: arm64: Add routing for NVHCR_EL2 trap Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 23/28] KVM: arm64: Add NVHCR_EL2 context switching Marc Zyngier
2026-07-14 10:03   ` sashiko-bot
2026-07-14  9:16 ` [PATCH v2 24/28] KVM: arm64: Engage NV3 ERET trap elision Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 25/28] KVM: arm64: Engage NV3 TLBI " Marc Zyngier
2026-07-14  9:16 ` [PATCH v2 26/28] KVM: arm64: Add FEAT_NV3 detection Marc Zyngier
2026-07-14 10:07   ` sashiko-bot
2026-07-14  9:16 ` [PATCH v2 27/28] KVM: arm64: Expose FEAT_NV3 to guests Marc Zyngier
2026-07-14 10:15   ` sashiko-bot
2026-07-14  9:16 ` [PATCH v2 28/28] arm64: Add override for ID_AA64MMFR4_EL1.NV_frac 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=20260714091641.1970822-17-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=oupton@kernel.org \
    --cc=seiden@linux.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox