[PATCH v3 15/19] arm/arm64: KVM: add opaque private pointer to MMIO accessors

Christoffer Dall christoffer.dall at linaro.org
Tue Nov 4 07:44:14 PST 2014

On Fri, Oct 31, 2014 at 05:26:50PM +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, extend them to
> take an opaque private pointer parameter.
> For the current GICv2 emulation we ignore it and simply pass NULL
> on the call.
> Signed-off-by: Andre Przywara <andre.przywara at arm.com>

Why does it have to be an opaque private pointer?  Would it not always
be a struct vcpu * or a vcpu_id then?


More information about the linux-arm-kernel mailing list