From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
kvm@vger.kernel.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>,
Andre Przywara <andre.przywara@arm.com>,
Eric Auger <eric.auger@redhat.com>
Subject: [PATCH v2 13/17] KVM: arm64: nv: Request vPE doorbell upon nested ERET to L2
Date: Sun, 12 Jan 2025 17:08:41 +0000 [thread overview]
Message-ID: <20250112170845.1181891-14-maz@kernel.org> (raw)
In-Reply-To: <20250112170845.1181891-1-maz@kernel.org>
From: Oliver Upton <oliver.upton@linux.dev>
Running an L2 guest with GICv4 enabled goes absolutely nowhere, and gets
into a vicious cycle of nested ERET followed by nested exception entry
into the L1.
When KVM does a put on a runnable vCPU, it marks the vPE as nonresident
but does not request a doorbell IRQ. Behind the scenes in the ITS
driver's view of the vCPU, its_vpe::pending_last gets set to true to
indicate that context is still runnable.
This comes to a head when doing the nested ERET into L2. The vPE doesn't
get scheduled on the redistributor as it is exclusively part of the L1's
VGIC context. kvm_vgic_vcpu_pending_irq() returns true because the vPE
appears runnable, and KVM does a nested exception entry into the L1
before L2 ever gets off the ground.
This issue can be papered over by requesting a doorbell IRQ when
descheduling a vPE as part of a nested ERET. KVM needs this anyway to
kick the vCPU out of the L2 when an IRQ becomes pending for the L1.
Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
Link: https://lore.kernel.org/r/20240823212703.3576061-4-oliver.upton@linux.dev
Signed-off-by: Marc Zyngier <maz@kernel.org>
---
arch/arm64/include/asm/kvm_host.h | 2 ++
arch/arm64/kvm/emulate-nested.c | 2 ++
arch/arm64/kvm/vgic/vgic-v4.c | 18 +++++++++++++++++-
3 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/include/asm/kvm_host.h b/arch/arm64/include/asm/kvm_host.h
index cb969c096d7bd..18d9166761972 100644
--- a/arch/arm64/include/asm/kvm_host.h
+++ b/arch/arm64/include/asm/kvm_host.h
@@ -958,6 +958,8 @@ struct kvm_vcpu_arch {
#define PMUSERENR_ON_CPU __vcpu_single_flag(sflags, BIT(4))
/* WFI instruction trapped */
#define IN_WFI __vcpu_single_flag(sflags, BIT(5))
+/* KVM is currently emulating a nested ERET */
+#define IN_NESTED_ERET __vcpu_single_flag(sflags, BIT(6))
/* Pointer to the vcpu's SVE FFR for sve_{save,load}_state() */
diff --git a/arch/arm64/kvm/emulate-nested.c b/arch/arm64/kvm/emulate-nested.c
index c460b8403aec5..69233dcc81a46 100644
--- a/arch/arm64/kvm/emulate-nested.c
+++ b/arch/arm64/kvm/emulate-nested.c
@@ -2434,6 +2434,7 @@ void kvm_emulate_nested_eret(struct kvm_vcpu *vcpu)
}
preempt_disable();
+ vcpu_set_flag(vcpu, IN_NESTED_ERET);
kvm_arch_vcpu_put(vcpu);
if (!esr_iss_is_eretax(esr))
@@ -2445,6 +2446,7 @@ void kvm_emulate_nested_eret(struct kvm_vcpu *vcpu)
*vcpu_cpsr(vcpu) = spsr;
kvm_arch_vcpu_load(vcpu, smp_processor_id());
+ vcpu_clear_flag(vcpu, IN_NESTED_ERET);
preempt_enable();
kvm_pmu_nested_transition(vcpu);
diff --git a/arch/arm64/kvm/vgic/vgic-v4.c b/arch/arm64/kvm/vgic/vgic-v4.c
index eedecbbbcf31b..0d9fb235c0180 100644
--- a/arch/arm64/kvm/vgic/vgic-v4.c
+++ b/arch/arm64/kvm/vgic/vgic-v4.c
@@ -336,6 +336,22 @@ void vgic_v4_teardown(struct kvm *kvm)
its_vm->vpes = NULL;
}
+static inline bool vgic_v4_want_doorbell(struct kvm_vcpu *vcpu)
+{
+ if (vcpu_get_flag(vcpu, IN_WFI))
+ return true;
+
+ if (likely(!vcpu_has_nv(vcpu)))
+ return false;
+
+ /*
+ * GICv4 hardware is only ever used for the L1. Mark the vPE (i.e. the
+ * L1 context) nonresident and request a doorbell to kick us out of the
+ * L2 when an IRQ becomes pending.
+ */
+ return vcpu_get_flag(vcpu, IN_NESTED_ERET);
+}
+
int vgic_v4_put(struct kvm_vcpu *vcpu)
{
struct its_vpe *vpe = &vcpu->arch.vgic_cpu.vgic_v3.its_vpe;
@@ -343,7 +359,7 @@ int vgic_v4_put(struct kvm_vcpu *vcpu)
if (!vgic_supports_direct_msis(vcpu->kvm) || !vpe->resident)
return 0;
- return its_make_vpe_non_resident(vpe, !!vcpu_get_flag(vcpu, IN_WFI));
+ return its_make_vpe_non_resident(vpe, vgic_v4_want_doorbell(vcpu));
}
int vgic_v4_load(struct kvm_vcpu *vcpu)
--
2.39.2
next prev parent reply other threads:[~2025-01-12 17:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 17:08 [PATCH v2 00/17] KVM: arm64: Add NV GICv3 support Marc Zyngier
2025-01-12 17:08 ` [PATCH v2 01/17] arm64: sysreg: Add layout for ICH_HCR_EL2 Marc Zyngier
2025-01-15 18:39 ` Andre Przywara
2025-01-12 17:08 ` [PATCH v2 02/17] arm64: sysreg: Add layout for ICH_VTR_EL2 Marc Zyngier
2025-01-15 18:40 ` Andre Przywara
2025-01-12 17:08 ` [PATCH v2 03/17] arm64: sysreg: Add layout for ICH_MISR_EL2 Marc Zyngier
2025-01-15 18:41 ` Andre Przywara
2025-01-12 17:08 ` [PATCH v2 04/17] KVM: arm64: Move host SVE/SME state flags out of vCPU Marc Zyngier
2025-01-12 17:08 ` [PATCH v2 05/17] KVM: arm64: nv: Load timer before the GIC Marc Zyngier
2025-01-12 17:08 ` [PATCH v2 06/17] KVM: arm64: nv: Add ICH_*_EL2 registers to vpcu_sysreg Marc Zyngier
2025-01-12 17:08 ` [PATCH v2 07/17] KVM: arm64: nv: Plumb handling of GICv3 EL2 accesses Marc Zyngier
2025-01-12 17:08 ` [PATCH v2 08/17] KVM: arm64: nv: Sanitise ICH_HCR_EL2 accesses Marc Zyngier
2025-01-12 17:08 ` [PATCH v2 09/17] KVM: arm64: nv: Nested GICv3 emulation Marc Zyngier
2025-01-12 17:08 ` [PATCH v2 10/17] KVM: arm64: nv: Handle L2->L1 transition on interrupt injection Marc Zyngier
2025-01-12 17:08 ` [PATCH v2 11/17] KVM: arm64: nv: Add Maintenance Interrupt emulation Marc Zyngier
2025-01-12 17:08 ` [PATCH v2 12/17] KVM: arm64: nv: Respect virtual HCR_EL2.TWx setting Marc Zyngier
2025-01-12 17:08 ` Marc Zyngier [this message]
2025-01-12 17:08 ` [PATCH v2 14/17] KVM: arm64: nv: Propagate used_lrs between L1 and L0 contexts Marc Zyngier
2025-01-12 17:08 ` [PATCH v2 15/17] KVM: arm64: nv: Fold GICv3 host trapping requirements into guest setup Marc Zyngier
2025-01-12 17:08 ` [PATCH v2 16/17] KVM: arm64: nv: Allow userland to set VGIC maintenance IRQ Marc Zyngier
2025-01-12 17:08 ` [PATCH v2 17/17] KVM: arm64: nv: Fail KVM init if asking for NV without GICv3 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=20250112170845.1181891-14-maz@kernel.org \
--to=maz@kernel.org \
--cc=andre.przywara@arm.com \
--cc=eric.auger@redhat.com \
--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=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