[PATCH v1 2/2] KVM: arm64: selftests: Add an ITS MOVALL test

[Fuad Tabba]

Hi Marc,

On Wed, 30 Sept 2026 at 13:21, Marc Zyngier <maz at kernel.org> wrote:
>
> On Tue, 29 Sep 2026 20:04:52 +0100,
> Fuad Tabba <fuad.tabba at linux.dev> wrote:
> >
> > Map LPI A to vCPU0's collection and LPI B to vCPU1's, remap vCPU0's
> > collection to vCPU2 and MOVALL vCPU0's LPIs there, then inject both. A
> > must be taken on vCPU2 and B on vCPU1. KVM's MAPC handling already moves
> > A to vCPU2, so only MOVALL handling can move B: without "KVM: arm64:
> > vgic-its: Fix MOVALL handling of source redistributor", it moves B to
> > vCPU2 as well.
>
> MOVALL is about moving the pending bits (see 5.3.13 in the IHI0069H.b
> spec).  Doing MOVALL first and only then injecting the interrupts
> doesn't quite check the MOVALL requirement. That doesn't impact KVM
> itself (we don't use pending tables at all), but you probably don't
> want to hardcode implementation specific behaviours here.

Ack.

[...]
>
> There seem to be a lot of commonality with the existing
> vgic_lpi_stress test.  I'd rather we make this test the container for
> most ITS-related tests, instead of coming up with new individual
> tests.

If you think this test is worth having, I'll respin v2 that way.

Cheers,
/fuad

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