[PATCH v2 42/52] KVM: arm/arm64: GICv4: Handle MOVI applied to a VLPI

From: Marc Zyngier
Date: Wed Jun 28 2017 - 11:11:14 EST


When the guest issues a MOVI, we need to tell the physical ITS
that we're now targetting a new vcpu. This is done by extracting
the current mapping, updating the target, and reapplying the
mapping. The core ITS code should do the right thing.

Signed-off-by: Marc Zyngier <marc.zyngier@xxxxxxx>
---
virt/kvm/arm/vgic/vgic-its.c | 13 +++++++++++++
1 file changed, 13 insertions(+)

diff --git a/virt/kvm/arm/vgic/vgic-its.c b/virt/kvm/arm/vgic/vgic-its.c
index ed52b94e8e6d..ee8355991bb1 100644
--- a/virt/kvm/arm/vgic/vgic-its.c
+++ b/virt/kvm/arm/vgic/vgic-its.c
@@ -706,6 +706,19 @@ static int vgic_its_cmd_handle_movi(struct kvm *kvm, struct vgic_its *its,
ite->irq->target_vcpu = vcpu;
spin_unlock(&ite->irq->irq_lock);

+ if (ite->irq->hw) {
+ struct its_vlpi_map map;
+ int ret;
+
+ ret = its_get_vlpi(ite->irq->host_irq, &map);
+ if (ret)
+ return ret;
+
+ map.vpe_idx = vcpu->vcpu_id;
+
+ return its_map_vlpi(ite->irq->host_irq, &map);
+ }
+
return 0;
}

--
2.11.0