abd7229626
We don't need to stop a specific VCPU when changing the active state, because private IRQs can only be modified by a running VCPU for the VCPU itself and it is therefore already stopped. However, it is also possible for two VCPUs to be modifying the active state of SPIs at the same time, which can cause the thread being stuck in the loop that checks other VCPU threads for a potentially very long time, or to modify the active state of a running VCPU. Fix this by serializing all accesses to setting and clearing the active state of interrupts using the KVM mutex. Reported-by: Andrew Jones <drjones@redhat.com> Signed-off-by: Christoffer Dall <cdall@linaro.org> Reviewed-by: Marc Zyngier <marc.zyngier@arm.com> |
||
|---|---|---|
| .. | ||
| 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.c | ||
| vgic.h | ||