From: Oliver Upton <oupton@kernel.org>
To: kvmarm@lists.linux.dev
Cc: Marc Zyngier <maz@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Wei-Lin Chang <weilin.chang@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Fuad Tabba <fuad.tabba@linux.dev>,
Oliver Upton <oupton@kernel.org>
Subject: [PATCH 0/4] KVM: arm64: vgic: Stop migrating IRQ from vgic_prune_ap_list()
Date: Tue, 29 Sep 2026 14:29:21 -0700 [thread overview]
Message-ID: <20260929212925.31775-1-oupton@kernel.org> (raw)
The VGIC has been getting a lot of undesired attention lately, as
there's plenty of weird and wonderful ways that the guest can play games
with KVM. My general impression on the whole matter is that modifying AP
lists remotely is a giant mess, with the worst offender being
vgic_prune_ap_list().
This series aims to sidestep the issue by only recalling IRQs from an AP
list if the vCPU has been paused. Keeping the overheads reasonable also
means adding support for pausing a single vCPU instead of the entire
VM, so update the eligible users of kvm_arm_halt_guest() to something
more relaxed while we're at it.
Marc, this series applies on top of your own for LPI malice [1]. You'll
note that I've taken some of it for 7.3 while leaving the rest for you
to take in 7.4, I'm perfectly happy with Patch 3 and 4 getting squashed
into the corresponding bits of your own series if you prefer.
Tested semi-rigorously on an Altra machine and the Orion board, using
both real guests and an LLM-generated selftest specific for migrating
pending LPIs. The latter was way too big to make sense of, I'll try and
post a test if I can it into something tidy.
[1]: https://lore.kernel.org/kvmarm/20260929093548.3598547-1-maz@kernel.org/
Oliver Upton (4):
KVM: arm64: Add helpers to halt a vCPU
KVM: arm64: vgic: Move IRQ migrations out of vgic_prune_ap_list()
KVM: arm64: vgic-v3: Only pause the targeted vCPU when disabling LPIs
KVM: arm64: vgic-v3: Pause the source vCPU when processing MOVALL cmd
arch/arm64/include/asm/kvm_host.h | 2 +
arch/arm64/kvm/arm.c | 18 ++-
arch/arm64/kvm/vgic/vgic-its.c | 19 ++-
arch/arm64/kvm/vgic/vgic-mmio-v2.c | 11 +-
arch/arm64/kvm/vgic/vgic-mmio-v3.c | 18 ++-
arch/arm64/kvm/vgic/vgic.c | 184 +++++++++++++++++------------
arch/arm64/kvm/vgic/vgic.h | 24 ++++
include/kvm/arm_vgic.h | 1 +
8 files changed, 164 insertions(+), 113 deletions(-)
base-commit: cfaf3b76669d386912a91103671691692f81c316
--
2.47.3
next reply other threads:[~2026-09-29 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 21:29 Oliver Upton [this message]
2026-09-29 21:29 ` [PATCH 1/4] KVM: arm64: Add helpers to halt a vCPU Oliver Upton
2026-09-30 13:33 ` Fuad Tabba
2026-09-29 21:29 ` [PATCH 2/4] KVM: arm64: vgic: Move IRQ migrations out of vgic_prune_ap_list() Oliver Upton
2026-09-30 13:55 ` Fuad Tabba
2026-09-30 21:50 ` Oliver Upton
2026-09-29 21:29 ` [PATCH 3/4] KVM: arm64: vgic-v3: Only pause the targeted vCPU when disabling LPIs Oliver Upton
2026-09-29 21:29 ` [PATCH 4/4] KVM: arm64: vgic-v3: Pause the source vCPU when processing MOVALL cmd Oliver Upton
2026-09-30 13:25 ` [PATCH 0/4] KVM: arm64: vgic: Stop migrating IRQ from vgic_prune_ap_list() Fuad Tabba
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=20260929212925.31775-1-oupton@kernel.org \
--to=oupton@kernel.org \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=weilin.chang@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.