From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49798) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VQay5-0008C8-Go for qemu-devel@nongnu.org; Mon, 30 Sep 2013 06:44:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VQaxz-0007se-H5 for qemu-devel@nongnu.org; Mon, 30 Sep 2013 06:44:45 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49979) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VQaxz-0007sX-92 for qemu-devel@nongnu.org; Mon, 30 Sep 2013 06:44:39 -0400 Message-ID: <52495611.4010308@redhat.com> Date: Mon, 30 Sep 2013 06:44:33 -0400 From: Laine Stump MIME-Version: 1.0 References: <524162DE.1080705@redhat.com> <20130925070116.GA5436@redhat.com> <1380098908.1968.30.camel@localhost.localdomain> <87txh62nyz.fsf@blackfin.pond.sub.org> <20130928181241.GA617@redhat.com> <8761tiiqfw.fsf@blackfin.pond.sub.org> In-Reply-To: <8761tiiqfw.fsf@blackfin.pond.sub.org> Content-Type: text/plain; charset=ISO-8859-9 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Attaching PCI devices to the PCIe root complex List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: =?ISO-8859-9?Q?Andreas_F=E4rb?= =?ISO-8859-9?Q?er?= , marcel.a@redhat.com, qemu list , Anthony Liguori , "Michael S. Tsirkin" On 09/30/2013 05:55 AM, Markus Armbruster wrote: > "Michael S. Tsirkin" writes: >> I never heard of a pci/pci express >> one but it's not impossible I think. > PCI on one side of the card, PCIe on the other, and a switchable > backplate? Weird :) > > Again, I can't see why we'd want to model this, even if it existed. Unfortunately that's what's been done, so libvirt will have to deal with it, even after qemu gets it fixed. > The current interface munges together all PCIish connectors, and the > result is a mess: users can't see which device can be plugged into which > socket. Libvirt needs to know, and it has grown a bunch of hardcoded ad > hoc rules, which aren't quite right. The good news is that libvirt has only recently started dealing with anything other than vanilla PCI slots. The bad news is that it has. I guess everything should work out okay if we just keep the current "wild guess" code around, but only fall back on it if the new more accurate information is unavailable.