From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36688) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UqkwY-0004Tj-5X for qemu-devel@nongnu.org; Sun, 23 Jun 2013 10:07:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UqkwV-000379-UC for qemu-devel@nongnu.org; Sun, 23 Jun 2013 10:07:02 -0400 Date: Sun, 23 Jun 2013 17:07:36 +0300 From: "Michael S. Tsirkin" Message-ID: <20130623140736.GB20842@redhat.com> References: <1371737338-25148-1-git-send-email-aik@ozlabs.ru> <874ncshh67.fsf@codemonkey.ws> <51C39578.6020204@ozlabs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51C39578.6020204@ozlabs.ru> 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: Alexey Kardashevskiy Cc: Anthony Liguori , qemu-trivial@nongnu.org, qemu-devel@nongnu.org, Alexander Graf , Alex Williamson , qemu-ppc@nongnu.org, Paolo Bonzini , Paul Mackerras , David Gibson On Fri, Jun 21, 2013 at 09:51:20AM +1000, Alexey Kardashevskiy wrote: > And kvm_irqchip_add_msi_route does not have any link to a device or a bus > so I'll have to walk through all PHBs in system and see if PHB's MSI window > is the one from MSIMessage and convert MSIMessage to virq. Pretty easy and > quick but still dirty hack, would it be better? 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. -- MST