summaryrefslogtreecommitdiffstats
path: root/arch/arm64/include
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2021-08-19 20:03:05 +0200
committerMarc Zyngier <maz@kernel.org>2021-08-20 09:53:22 +0200
commit3134cc8beb69d0db9de651081707c4651c011621 (patch)
tree1bad753625d699ee7f133bb3dae5d82ccc2374c5 /arch/arm64/include
parentKVM: arm64: vgic: Drop WARN from vgic_get_irq (diff)
downloadlinux-3134cc8beb69d0db9de651081707c4651c011621.tar.xz
linux-3134cc8beb69d0db9de651081707c4651c011621.zip
KVM: arm64: vgic: Resample HW pending state on deactivation
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). If we don't do anything, the interrupt will be spuriously injected in the guest. Although this shouldn't have any ill effect (spurious interrupts are always possible), we can improve the emulation by detecting the deactivation-while-pending case and resample the interrupt. While we're at it, move the logic into a common helper that can be shared between the two GIC implementations. Fixes: e40cc57bac79 ("KVM: arm/arm64: vgic: Support level-triggered mapped interrupts") Reported-by: Raghavendra Rao Ananta <rananta@google.com> Tested-by: Raghavendra Rao Ananta <rananta@google.com> Reviewed-by: Oliver Upton <oupton@google.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Cc: stable@vger.kernel.org Link: https://lore.kernel.org/r/20210819180305.1670525-1-maz@kernel.org
Diffstat (limited to 'arch/arm64/include')
0 files changed, 0 insertions, 0 deletions