From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39504) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ur5ai-0000HA-M3 for qemu-devel@nongnu.org; Mon, 24 Jun 2013 08:09:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ur5af-0003jK-RH for qemu-devel@nongnu.org; Mon, 24 Jun 2013 08:09:52 -0400 Date: Mon, 24 Jun 2013 15:10:20 +0300 From: "Michael S. Tsirkin" Message-ID: <20130624121020.GA32114@redhat.com> References: <1371737338-25148-1-git-send-email-aik@ozlabs.ru> <874ncshh67.fsf@codemonkey.ws> <51C39578.6020204@ozlabs.ru> <20130623140736.GB20842@redhat.com> <1372023385.3944.108.camel@pasglop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1372023385.3944.108.camel@pasglop> Subject: Re: [Qemu-devel] [PATCH] RFC kvm irqfd: add directly mapped MSI IRQ support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Benjamin Herrenschmidt Cc: Anthony Liguori , Alexey Kardashevskiy , qemu-devel@nongnu.org, Alexander Graf , qemu-trivial@nongnu.org, Alex Williamson , qemu-ppc@nongnu.org, Paolo Bonzini , Paul Mackerras , David Gibson On Mon, Jun 24, 2013 at 07:36:25AM +1000, Benjamin Herrenschmidt wrote: > On Sun, 2013-06-23 at 17:07 +0300, Michael S. Tsirkin wrote: > > Yes I think that's fine really. > > > > Basically devices all speak MSIMessage as they should - > > this is what the PCI spec says. > > On all normal systems guests also speak MSIMessage so > > the API which uses these makes sense for kvm. > > Except, ppc architecture in its wisdom decided to hide this > > in firmware. QEMU does not have firmware so the translation > > has to be maintained in QEMU powerpc code. > > It is still not enough. There is nothing that says that an MSI > address/message is unique. On pseries (among others I'm sure), this is a > per-host-bridge concept since the MSIs are decoded by the PHB and turned > into standard fabric interrupts there. > > So at least the bus needs to be passed as well. > > Cheers, > Ben. If passing bus (or dma context, etc) turns out to actually be helpful, why not. -- MST