Re: [PATCH 0/7] KVM: arm64: Fix cross-CPU vcpu pausing

[Marc Zyngier <maz@kernel.org>]

On Thu, 15 Oct 2026 13:57:12 +0100,
Fuad Tabba <fuad.tabba@linux.dev> wrote:
> 
> Hi Marc,
> 
> On Thu, 15 Oct 2026 11:05:32 +0100, Marc Zyngier <maz@kernel.org> wrote:
> [...]
> > This series addresses these defects, and builds on top of it to:
> >
> > - add pausing to a single vcpu in addition to the full VM pausing
> >
> > - convert LPI disabling and the MOVALL command to vcpu pausing
> >
> > Patches on top of -rc6, most of them being Cc stable without any
> > qualification (this has been broken for as long as I can remember).
> 
> I'll send a couple of nits on patches 2 and 5 as replies to those
> patches.

Thanks, I'll tidy that up as I apply them.

> 
> For the series:
> Reviewed-by: Fuad Tabba <fuad.tabba@linux.dev>
> 
> Tested on QEMU on top of -rc6: npVM and pVM boots in pKVM, npVM boots
> with nVHE and VHE hosts, and vgic_irq and vgic_lpi_stress in all three
> and with kvm-arm.mode=nested. My reproducer has vcpu 0 clear vcpu 1's
> EnableLPIs while the LPI is in vcpu 1's LR: on -rc6 the LPI is still
> pending on vcpu 1 afterwards, and with the series it isn't. With my
> vgic-its v2 [1] on top, my MOVALL selftest and my shared LPI and DISCARD
> reproducers pass, including with PROVE_LOCKING and with debug hooks
> that force the DISCARD race.
> 
> Tested-by: Fuad Tabba <fuad.tabba@linux.dev>

Great, thanks again.

> 
> v2 of "Fix LPI double mapping and DISCARD" [1] applies on top of this
> series as it is. Would you take it as it is, or would you like me to
> respin it?

I can stash it on top as is. Looks like the first set of 7.4 fixes is
going to be pretty vgic-heavy anyway.

Cheers,

	M.

-- 
Without deviation from the norm, progress is not possible.