Marc Zyngier a3f574cd65 KVM: arm64: vgic-v4: Plug race between non-residency and v4.1 doorbell ... When making a vPE non-resident because it has hit a blocking WFI, the doorbell can fire at any time after the write to the RD. Crucially, it can fire right between the write to GICR_VPENDBASER and the write to the pending_last field in the its_vpe structure. This means that we would overwrite pending_last with stale data, and potentially not wakeup until some unrelated event (such as a timer interrupt) puts the vPE back on the CPU. GICv4 isn't affected by this as we actively mask the doorbell on entering the guest, while GICv4.1 automatically manages doorbell delivery without any hypervisor-driven masking. Use the vpe_lock to synchronize such update, which solves the problem altogether. Fixes: ae699ad348 ("irqchip/gic-v4.1: Move doorbell management to the GICv4 abstraction layer") Reported-by: Zenghui Yu <yuzenghui@huawei.com> Signed-off-by: Marc Zyngier <maz@kernel.org>		2020-06-23 11:24:39 +01:00
..
trace.h
vgic-debug.c
vgic-init.c
vgic-irqfd.c
vgic-its.c
vgic-kvm-device.c
vgic-mmio-v2.c
vgic-mmio-v3.c
vgic-mmio.c
vgic-mmio.h
vgic-v2.c
vgic-v3.c
vgic-v4.c
vgic.c
vgic.h