arm/arm64: KVM: Initialize the vgic on-demand when injecting IRQs
authorChristoffer Dall <christoffer.dall@linaro.org>
Tue, 9 Dec 2014 13:35:33 +0000 (14:35 +0100)
committerChristoffer Dall <christoffer.dall@linaro.org>
Mon, 15 Dec 2014 10:36:21 +0000 (11:36 +0100)
commitca7d9c829d419c06e450afa5f785d58198c37caa
tree04f7fd0e5f7e6469c93056534cf5142cfa80ef3b
parent716139df2517fbc3f2306dbe8eba0fa88dca0189
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>
virt/kvm/arm/vgic.c