From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39846) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QvTqd-0004bh-RO for qemu-devel@nongnu.org; Mon, 22 Aug 2011 08:43:24 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QvTqc-0002qq-Ug for qemu-devel@nongnu.org; Mon, 22 Aug 2011 08:43:23 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58281) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QvTqc-0002qg-G1 for qemu-devel@nongnu.org; Mon, 22 Aug 2011 08:43:22 -0400 Message-ID: <4E524EBB.8090603@redhat.com> Date: Mon, 22 Aug 2011 15:42:35 +0300 From: Avi Kivity MIME-Version: 1.0 References: <1312308847.2653.467.camel@bling.home> <1312310121.2653.470.camel@bling.home> <20110803020422.GF29719@yookeroo.fritz.box> <4E3F9E33.5000706@redhat.com> <1312932258.4524.55.camel@bling.home> <1312944513.29273.28.camel@pasglop> <1313859105.6866.192.camel@x201.home> <4E51F782.7060005@redhat.com> <20110822104635.GC2079@amd.com> <4E5234B7.7000700@redhat.com> <20110822123651.GD2079@amd.com> In-Reply-To: <20110822123651.GD2079@amd.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] kvm PCI assignment & VFIO ramblings List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Roedel, Joerg" Cc: Alexey Kardashevskiy , "kvm@vger.kernel.org" , Paul Mackerras , qemu-devel , iommu , chrisw , Alex Williamson , "linux-pci@vger.kernel.org" , linuxppc-dev , "benve@cisco.com" On 08/22/2011 03:36 PM, Roedel, Joerg wrote: > On Mon, Aug 22, 2011 at 06:51:35AM -0400, Avi Kivity wrote: > > On 08/22/2011 01:46 PM, Joerg Roedel wrote: > > > That does not work. The bridge in question may not even be visible as a > > > PCI device, so you can't link to it. This is the case on a few PCIe > > > cards which only have a PCIx chip and a PCIe-2-PCIx bridge to implement > > > the PCIe interface (yes, I have seen those cards). > > > > How does the kernel detect that devices behind the invisible bridge must > > be assigned as a unit? > > On the AMD IOMMU side this information is stored in the IVRS ACPI table. > Not sure about the VT-d side, though. > I see. There is no sysfs node representing it? I'd rather not add another meaningless identifier. -- error compiling committee.c: too many arguments to function