Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753840AbaLDKCu (ORCPT ); Thu, 4 Dec 2014 05:02:50 -0500 Received: from mail-la0-f53.google.com ([209.85.215.53]:40784 "EHLO mail-la0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753815AbaLDKCr (ORCPT ); Thu, 4 Dec 2014 05:02:47 -0500 MIME-Version: 1.0 In-Reply-To: <547DFCD6.3000406@linaro.org> References: <1417541251-20761-1-git-send-email-eric.auger@linaro.org> <547DFCD6.3000406@linaro.org> From: Peter Maydell Date: Thu, 4 Dec 2014 10:02:25 +0000 Message-ID: Subject: Re: [PATCH] KVM: arm/arm64: vgic: add init entry to VGIC KVM device To: Eric Auger Cc: eric.auger@st.com, Christoffer Dall , Marc Zyngier , arm-mail-list , "kvmarm@lists.cs.columbia.edu" , kvm-devel , Alex Williamson , Alexander Graf , "gleb@kernel.org" , Paolo Bonzini , lkml - Kernel Mailing List , Patch Tracking Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2 December 2014 at 17:54, Eric Auger wrote: > as soon as VFIO signaling is set up (the device IRQ index is linked to > an eventfd, the physical IRQ VFIO handler is installed and the physical > IRQ is enabled at interrupt controller level), virtual IRQs are likely > to be injected. With current QEMU code, we setup this VFIO signaling > *before* the vgic readiness (either on machine init done or reset > notifier) and we face that issue of early injection. QEMU related > patches to follow ... So can you describe in QEMU terms how the lifecycle of these things works? How do we ensure that we don't start trying to inject VFIO IRQs before we've even created the vgic, for instance? thanks -- PMM -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/