From: Eduardo Habkost <ehabkost@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: aik@ozlabs.ru, marcel@redhat.com, lersek@redhat.com,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [RFC for-2.10 0/3] Rework handling of PCI/PCIe "hybrid" devices
Date: Tue, 29 Aug 2017 10:01:59 -0300 [thread overview]
Message-ID: <20170829130159.GW15315@localhost.localdomain> (raw)
In-Reply-To: <20170328021651.19350-1-david@gibson.dropbear.id.au>
On Tue, Mar 28, 2017 at 01:16:48PM +1100, David Gibson wrote:
> A couple of devices - virtio-pci and XHCI - can present themselves to
> the guest as either PCI or PCIe devices depending on how they're
> attached. However, the logic is a little different between the two
> devices. In addition the logic in virtio makes it difficult to put a
> PCIe virtio device into a "pseries" guest because of the unusual way
> the paravirtualized PCI bus works there.
virtio-pci and xhci are not the only hybrid devices. What about
vmxnet3, pvscsi, and vfio-pci?
>
> This series makes the logic more consistent, and allows per-machine
> overrides to address that.
>
> Currently patch 3/3 shows a non-obvious side effect of this change. A
> PCIe virtio device is, by default, modern mode only, but the qtest
> logic doesn't handle modern-only virtio devices correctly. We work
> around this by explicitly adding disable-legacy=off to the testcases.
> It would probably be better to update libqos so that it can handle
> modern virtio devices.
>
> David Gibson (3):
> pci/pcie: Make a consistent helper for switching PCI/PCIe "hybrid"
> devices
> pci: Allow host bridges to override PCI/PCIe hybrid device behaviour
> pseries: Allow PCIe virtio and XHCI on pseries machine type
>
> hw/pci/pci.c | 14 ++++++++++++++
> hw/ppc/spapr_pci.c | 9 +++++++++
> hw/usb/hcd-xhci.c | 2 +-
> hw/virtio/virtio-pci.c | 3 +--
> include/hw/pci/pci.h | 1 +
> include/hw/pci/pci_host.h | 1 +
> tests/virtio-9p-test.c | 2 +-
> tests/virtio-blk-test.c | 4 ++--
> tests/virtio-net-test.c | 2 +-
> tests/virtio-scsi-test.c | 2 +-
> 10 files changed, 32 insertions(+), 8 deletions(-)
>
> --
> 2.9.3
>
>
--
Eduardo
prev parent reply other threads:[~2017-08-29 13:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 2:16 [Qemu-devel] [RFC for-2.10 0/3] Rework handling of PCI/PCIe "hybrid" devices David Gibson
2017-03-28 2:16 ` [Qemu-devel] [RFC for-2.10 1/3] pci/pcie: Make a consistent helper for switching " David Gibson
2017-04-19 17:48 ` Marcel Apfelbaum
2017-04-26 15:23 ` Michael S. Tsirkin
2017-05-01 6:53 ` David Gibson
2017-08-29 11:42 ` David Gibson
2017-08-29 14:12 ` Eduardo Habkost
2017-08-30 5:54 ` David Gibson
2017-08-30 12:23 ` Eduardo Habkost
2017-09-26 5:04 ` David Gibson
2017-03-28 2:16 ` [Qemu-devel] [RFC for-2.10 2/3] pci: Allow host bridges to override PCI/PCIe hybrid device behaviour David Gibson
2017-04-17 18:30 ` Eduardo Habkost
2017-04-18 2:21 ` David Gibson
2017-04-18 14:33 ` Eduardo Habkost
2017-04-19 18:04 ` Marcel Apfelbaum
2017-04-26 15:29 ` Michael S. Tsirkin
2017-05-01 6:56 ` David Gibson
2017-09-28 7:53 ` David Gibson
2017-03-28 2:16 ` [Qemu-devel] [RFC for-2.10 3/3] pseries: Allow PCIe virtio and XHCI on pseries machine type David Gibson
2017-03-29 2:20 ` Alexey Kardashevskiy
2017-03-29 4:07 ` David Gibson
2017-08-29 13:01 ` Eduardo Habkost [this message]
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=20170829130159.GW15315@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=lersek@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).