arm/arm64: KVM: Initialize the vgic on-demand when injecting IRQs
authorChristoffer Dall <christoffer.dall@linaro.org>
Mon, 4 May 2015 01:25:16 +0000 (09:25 +0800)
committerSasha Levin <sasha.levin@oracle.com>
Mon, 11 May 2015 11:07:34 +0000 (07:07 -0400)
commit11d483cec89a33c6fc1bdd08901b0da723d6f2b9
tree0f249be3c3cedaafa1e4e42bec0367fa4f21eb20
parentd4d53f72fa6bcb4a92a134bed97b07ea3e154840
arm/arm64: KVM: Initialize the vgic on-demand when injecting IRQs

commit ca7d9c829d419c06e450afa5f785d58198c37caa upstream.

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>
Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
Signed-off-by: Sasha Levin <sasha.levin@oracle.com>
virt/kvm/arm/vgic.c