On Fri, 27 Jan 2023 07:54:47 +0800, Gavin Shan wrote:
> It has been known case where no running VCPU context exists when the
> vgic/its tables are saved. There are other two unknown cases where we
> don't have the running VCPU context: (a) restore vgic3 LPI pending
> status. (b) restoring vgic3 pending tables.
>
> PATCH[1] includes 'kvm_mmu.h' to 'vgic.h'
> PATCH[2] adds unified helper vgic_write_guest_lock()
> PATCH[3 - 4] allows no-running-vcpu context for (a) and (b)
>
> [...]
Applied to fixes, thanks!
[2/4] KVM: arm64: Add helper vgic_write_guest_lock()
commit: a23eaf9368aafa4defcc8904b20391b6ea07bb1e
[3/4] KVM: arm64: Allow no running vcpu on restoring vgic3 LPI pending status
commit: 2f8b1ad2228a7f1f1e2458864f4bfc1cbdf511ed
[4/4] KVM: arm64: Allow no running vcpu on saving vgic3 pending table
commit: 6028acbe3a5f2119a2a6ddd3e06453c87c09cae0
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
