Andre Przywara 9fedf14677 arm/arm64: KVM: add opaque private pointer to MMIO data ... For a GICv2 there is always only one (v)CPU involved: the one that does the access. On a GICv3 the access to a CPU redistributor is memory-mapped, but not banked, so the (v)CPU affected is determined by looking at the MMIO address region being accessed. To allow passing the affected CPU into the accessors later, extend struct kvm_exit_mmio to add an opaque private pointer parameter. The current GICv2 emulation just does not use it. Signed-off-by: Andre Przywara <andre.przywara@arm.com> Acked-by: Christoffer Dall <christoffer.dall@linaro.org> Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>		2015-01-20 18:25:30 +01:00
..
arch_timer.c	arm/arm64: KVM: Require in-kernel vgic for the arch timers	2014-12-15 11:50:42 +01:00
vgic-v2-emul.c	arm/arm64: KVM: split GICv2 specific emulation code from vgic.c	2015-01-20 18:25:30 +01:00
vgic-v2.c	arm/arm64: KVM: make the maximum number of vCPUs a per-VM value	2015-01-20 18:25:28 +01:00
vgic-v3.c	arm/arm64: KVM: make the value of ICC_SRE_EL1 a per-VM variable	2015-01-20 18:25:28 +01:00
vgic.c	arm/arm64: KVM: add opaque private pointer to MMIO data	2015-01-20 18:25:30 +01:00
vgic.h	arm/arm64: KVM: add vgic.h header file	2015-01-20 18:25:30 +01:00