Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752651AbdGaRdy (ORCPT ); Mon, 31 Jul 2017 13:33:54 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:56812 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752368AbdGaR2Y (ORCPT ); Mon, 31 Jul 2017 13:28:24 -0400 From: Marc Zyngier To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org Cc: Christoffer Dall , Thomas Gleixner , Jason Cooper , Eric Auger , Shanker Donthineni , Mark Rutland , Shameerali Kolothum Thodi Subject: [PATCH v3 44/59] KVM: arm/arm64: GICv4: Handle MOVI applied to a VLPI Date: Mon, 31 Jul 2017 18:26:22 +0100 Message-Id: <20170731172637.29355-45-marc.zyngier@arm.com> X-Mailer: git-send-email 2.11.0 In-Reply-To: <20170731172637.29355-1-marc.zyngier@arm.com> References: <20170731172637.29355-1-marc.zyngier@arm.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 993 Lines: 36 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 --- 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 79bac93d3e7d..aaad577ce328 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