Christoffer Dall ca7d9c829d arm/arm64: KVM: Initialize the vgic on-demand when injecting IRQs ... Userspace assumes that it can wire up IRQ injections after having created all VCPUs and after having created the VGIC, but potentially before starting the first VCPU. This can currently lead to lost IRQs because the state of that IRQ injection is not stored anywhere and we don't return an error to userspace. We haven't seen this problem manifest itself yet, presumably because guests reset the devices on boot, but this could cause issues with migration and other non-standard startup configurations. Reviewed-by: Marc Zyngier <marc.zyngier@arm.com> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>		2014-12-15 11:36:21 +01:00
..
arch_timer.c	arm, kvm: fix double lock on cpu_add_remove_lock	2014-04-08 13:15:54 +02:00
vgic-v2.c	arm/arm64: KVM: Fix BE accesses to GICv2 EISR and ELRSR regs	2014-10-16 10:57:41 +02:00
vgic-v3.c	KVM: arm64: GICv3: mandate page-aligned GICV region	2014-07-31 15:59:40 +02:00
vgic.c	arm/arm64: KVM: Initialize the vgic on-demand when injecting IRQs	2014-12-15 11:36:21 +01:00