Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933004AbdHVOd5 (ORCPT ); Tue, 22 Aug 2017 10:33:57 -0400 Received: from mx1.redhat.com ([209.132.183.28]:35640 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932513AbdHVOdz (ORCPT ); Tue, 22 Aug 2017 10:33:55 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com A66B2883DE Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx02.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=eric.auger@redhat.com From: Auger Eric Subject: Re: [PATCH v2 5/8] KVM: arm/arm64: vgic: Handle mapped level sensitive SPIs To: Christoffer Dall References: <1497531160-29162-1-git-send-email-eric.auger@redhat.com> <1497531160-29162-6-git-send-email-eric.auger@redhat.com> <20170721121137.GF16350@cbox> Cc: eric.auger.pro@gmail.com, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu, alex.williamson@redhat.com, b.reynal@virtualopensystems.com, pbonzini@redhat.com, marc.zyngier@arm.com, christoffer.dall@linaro.org, drjones@redhat.com, wei@redhat.com Message-ID: <772938b1-607d-1f3b-83c0-95a3d687020d@redhat.com> Date: Tue, 22 Aug 2017 16:33:42 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20170721121137.GF16350@cbox> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Tue, 22 Aug 2017 14:33:55 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4315 Lines: 136 Hi Christoffer, On 21/07/2017 14:11, Christoffer Dall wrote: > On Thu, Jun 15, 2017 at 02:52:37PM +0200, Eric Auger wrote: >> Currently, the line level of unmapped level sensitive SPIs is >> toggled down by the maintenance IRQ handler/resamplefd mechanism. >> >> As mapped SPI completion is not trapped, we cannot rely on this >> mechanism and the line level needs to be observed at distributor >> level instead. >> >> This patch handles the physical IRQ case in vgic_validate_injection >> and get the line level of a mapped SPI at distributor level. >> >> Signed-off-by: Eric Auger >> >> --- >> >> v1 -> v2: >> - renamed is_unshared_mapped into is_mapped_spi >> - changes to kvm_vgic_map_phys_irq moved in the previous patch >> - make vgic_validate_injection more readable >> - reword the commit message >> --- >> virt/kvm/arm/vgic/vgic.c | 16 ++++++++++++++-- >> virt/kvm/arm/vgic/vgic.h | 7 ++++++- >> 2 files changed, 20 insertions(+), 3 deletions(-) >> >> diff --git a/virt/kvm/arm/vgic/vgic.c b/virt/kvm/arm/vgic/vgic.c >> index 075f073..2e35ac7 100644 >> --- a/virt/kvm/arm/vgic/vgic.c >> +++ b/virt/kvm/arm/vgic/vgic.c >> @@ -139,6 +139,17 @@ void vgic_put_irq(struct kvm *kvm, struct vgic_irq *irq) >> kfree(irq); >> } >> >> +bool irq_line_level(struct vgic_irq *irq) >> +{ >> + bool line_level = irq->line_level; >> + >> + if (unlikely(is_mapped_spi(irq))) >> + WARN_ON(irq_get_irqchip_state(irq->host_irq, >> + IRQCHIP_STATE_PENDING, >> + &line_level)); >> + return line_level; >> +} >> + >> /** >> * kvm_vgic_target_oracle - compute the target vcpu for an irq >> * >> @@ -236,13 +247,14 @@ static void vgic_sort_ap_list(struct kvm_vcpu *vcpu) >> >> /* >> * Only valid injection if changing level for level-triggered IRQs or for a >> - * rising edge. >> + * rising edge. Injection of virtual interrupts associated to physical >> + * interrupts always is valid. > > why? I don't remember this now, and that means I probably won't in the > future either. Sorry for the late reply. The life cycle of the physically mapped IRQ is as follows: - pIRQ becomes pending - pIRQ is acknowledged by the physical handler and becomes active - vIRQ gets injected as part of the physical handler chain (VFIO->irqfd kvm_vgic_inject_irq for instance). Linux irq cannot hit until vIRQ=pIRQ deactivation - guest deactivates the vIRQ which automatically deactivates the pIRQ So to me if we are about to vgic_validate_injection() an injection of a physically mapped vIRQ this means the vgic state is ready to accept it: previous occurence was deactivated. There cannot be any state inconsistency around the line_level/level. Do you agree? I will add this description at least in the commit message. > > When I look at this now, I'm thinking, if we're not going to change > anything, why proceed beyond validate injection? don't catch this one. validation always succeeds and then we further handle the IRQ. Thanks Eric > >> */ >> static bool vgic_validate_injection(struct vgic_irq *irq, bool level) >> { >> switch (irq->config) { >> case VGIC_CONFIG_LEVEL: >> - return irq->line_level != level; >> + return (irq->line_level != level || unlikely(is_mapped_spi(irq))); >> case VGIC_CONFIG_EDGE: >> return level; >> } >> diff --git a/virt/kvm/arm/vgic/vgic.h b/virt/kvm/arm/vgic/vgic.h >> index bba7fa2..da254ae 100644 >> --- a/virt/kvm/arm/vgic/vgic.h >> +++ b/virt/kvm/arm/vgic/vgic.h >> @@ -96,14 +96,19 @@ >> /* we only support 64 kB translation table page size */ >> #define KVM_ITS_L1E_ADDR_MASK GENMASK_ULL(51, 16) >> >> +bool irq_line_level(struct vgic_irq *irq); >> + >> static inline bool irq_is_pending(struct vgic_irq *irq) >> { >> if (irq->config == VGIC_CONFIG_EDGE) >> return irq->pending_latch; >> else >> - return irq->pending_latch || irq->line_level; >> + return irq->pending_latch || irq_line_level(irq); >> } >> >> +#define is_mapped_spi(i) \ >> +((i)->hw && (i)->intid >= VGIC_NR_PRIVATE_IRQS && (i)->intid < 1020) >> + > > nit: why is this not a static inline ? > >> /* >> * This struct provides an intermediate representation of the fields contained >> * in the GICH_VMCR and ICH_VMCR registers, such that code exporting the GIC >> -- >> 2.5.5 >> > > Thanks, > -Christoffer >