From: Laine Stump <laine@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Andreas Färber" <afaerber@suse.de>,
marcel.a@redhat.com, "qemu list" <qemu-devel@nongnu.org>,
"Anthony Liguori" <anthony@codemonkey.ws>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Attaching PCI devices to the PCIe root complex
Date: Mon, 30 Sep 2013 06:44:33 -0400 [thread overview]
Message-ID: <52495611.4010308@redhat.com> (raw)
In-Reply-To: <8761tiiqfw.fsf@blackfin.pond.sub.org>
On 09/30/2013 05:55 AM, Markus Armbruster wrote:
> "Michael S. Tsirkin" <mst@redhat.com> 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.
next prev parent reply other threads:[~2013-09-30 10:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 10:01 [Qemu-devel] Attaching PCI devices to the PCIe root complex Laine Stump
2013-09-25 7:01 ` Michael S. Tsirkin
2013-09-25 8:48 ` Marcel Apfelbaum
2013-09-25 8:59 ` Michael S. Tsirkin
2013-10-02 8:53 ` Paolo Bonzini
2013-10-02 9:28 ` Michael S. Tsirkin
2013-09-25 9:39 ` Laine Stump
2013-09-25 10:00 ` Michael S. Tsirkin
2013-09-25 10:14 ` Laine Stump
2013-09-25 10:56 ` Michael S. Tsirkin
2013-09-25 10:58 ` Michael S. Tsirkin
2013-09-27 17:06 ` Markus Armbruster
2013-09-28 18:12 ` Michael S. Tsirkin
2013-09-30 9:55 ` Markus Armbruster
2013-09-30 10:44 ` Laine Stump [this message]
2013-09-30 10:48 ` Michael S. Tsirkin
2013-09-30 16:01 ` Gerd Hoffmann
2013-09-30 16:06 ` Michael S. Tsirkin
2013-10-01 21:14 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52495611.4010308@redhat.com \
--to=laine@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=marcel.a@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).