Commit 9fedf146 authored by Andre Przywara's avatar Andre Przywara Committed by Christoffer Dall

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: default avatarAndre Przywara <andre.przywara@arm.com>
Acked-by: default avatarChristoffer Dall <christoffer.dall@linaro.org>
Signed-off-by: default avatarChristoffer Dall <christoffer.dall@linaro.org>
parent 1d916229
...@@ -37,6 +37,7 @@ struct kvm_exit_mmio { ...@@ -37,6 +37,7 @@ struct kvm_exit_mmio {
u8 data[8]; u8 data[8];
u32 len; u32 len;
bool is_write; bool is_write;
void *private;
}; };
static inline void kvm_prepare_mmio(struct kvm_run *run, static inline void kvm_prepare_mmio(struct kvm_run *run,
......
...@@ -40,6 +40,7 @@ struct kvm_exit_mmio { ...@@ -40,6 +40,7 @@ struct kvm_exit_mmio {
u8 data[8]; u8 data[8];
u32 len; u32 len;
bool is_write; bool is_write;
void *private;
}; };
static inline void kvm_prepare_mmio(struct kvm_run *run, static inline void kvm_prepare_mmio(struct kvm_run *run,
......
...@@ -709,6 +709,7 @@ static bool call_range_handler(struct kvm_vcpu *vcpu, ...@@ -709,6 +709,7 @@ static bool call_range_handler(struct kvm_vcpu *vcpu,
mmio32.len = 4; mmio32.len = 4;
mmio32.is_write = mmio->is_write; mmio32.is_write = mmio->is_write;
mmio32.private = mmio->private;
mmio32.phys_addr = mmio->phys_addr + 4; mmio32.phys_addr = mmio->phys_addr + 4;
if (mmio->is_write) if (mmio->is_write)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment