On 2021/3/25 2:19, Marc Zyngier wrote: > On Mon, 22 Mar 2021 14:01:52 +0800, Shenming Lu wrote: >> In GICv4.1, migration has been supported except for (directly-injected) >> VLPI. And GICv4.1 Spec explicitly gives a way to get the VLPI's pending >> state (which was crucially missing in GICv4.0). So we make VLPI migration >> capable on GICv4.1 in this series. >> >> In order to support VLPI migration, we need to save and restore all >> required configuration information and pending states of VLPIs. But >> in fact, the configuration information of VLPIs has already been saved >> (or will be reallocated on the dst host...) in vgic(kvm) migration. >> So we only have to migrate the pending states of VLPIs specially. >> >> [...] > > Applied to next, thanks! Thanks a lot again for all the comments and suggestions. :-) Shenming > > [1/6] irqchip/gic-v3-its: Add a cache invalidation right after vPE unmapping > commit: 301beaf19739cb6e640ed44e630e7da993f0ecc8 > [2/6] irqchip/gic-v3-its: Drop the setting of PTZ altogether > commit: c21bc068cdbe5613d3319ae171c3f2eb9f321352 > [3/6] KVM: arm64: GICv4.1: Add function to get VLPI state > commit: 80317fe4a65375fae668672a1398a0fb73eb9023 > [4/6] KVM: arm64: GICv4.1: Try to save VLPI state in save_pending_tables > commit: f66b7b151e00427168409f8c1857970e926b1e27 > [5/6] KVM: arm64: GICv4.1: Restore VLPI pending state to physical side > commit: 12df7429213abbfa9632ab7db94f629ec309a58b > [6/6] KVM: arm64: GICv4.1: Give a chance to save VLPI state > commit: 8082d50f4817ff6a7e08f4b7e9b18e5f8bfa290d > > Cheers, > > M. >
