On Thu, 19 Aug 2021 19:03:05 +0100, Marc Zyngier wrote:
> When a mapped level interrupt (a timer, for example) is deactivated
> by the guest, the corresponding host interrupt is equally deactivated.
> However, the fate of the pending state still needs to be dealt
> with in SW.
>
> This is specially true when the interrupt was in the active+pending
> state in the virtual distributor at the point where the guest
> was entered. On exit, the pending state is potentially stale
> (the guest may have put the interrupt in a non-pending state).
>
> [...]
Applied to next, thanks!
[1/1] KVM: arm64: vgic: Resample HW pending state on deactivation
commit: 3134cc8beb69d0db9de651081707c4651c011621
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
