[PATCH v4 14/19] arm/arm64: KVM: add opaque private pointer to MMIO data

Christoffer Dall christoffer.dall at linaro.org
Sun Nov 23 05:33:30 PST 2014

On Fri, Nov 14, 2014 at 10:07:58AM +0000, Andre Przywara wrote:
> 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 at arm.com>
> ---

Looks reasonable:

Acked-by: Christoffer Dall <christoffer.dall at linaro.org>

More information about the linux-arm-kernel mailing list