Christoffer Dall e1ba0207a1 ARM: KVM: Allow creating the VGIC after VCPUs ... Rework the VGIC initialization slightly to allow initialization of the vgic cpu-specific state even if the irqchip (the VGIC) hasn't been created by user space yet. This is safe, because the vgic data structures are already allocated when the CPU is allocated if VGIC support is compiled into the kernel. Further, the init process does not depend on any other information and the sacrifice is a slight performance degradation for creating VMs in the no-VGIC case. The reason is that the new device control API doesn't mandate creating the VGIC before creating the VCPU and it is unreasonable to require user space to create the VGIC before creating the VCPUs. At the same time move the irqchip_in_kernel check out of kvm_vcpu_first_run_init and into the init function to make the per-vcpu and global init functions symmetric and add comments on the exported functions making it a bit easier to understand the init flow by only looking at vgic.c. Acked-by: Marc Zyngier <marc.zyngier@arm.com> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>		2013-12-21 10:01:06 -08:00
..
arch_timer.c	ARM/KVM: save and restore generic timer registers	2013-12-21 10:00:15 -08:00
vgic.c	ARM: KVM: Allow creating the VGIC after VCPUs	2013-12-21 10:01:06 -08:00