From: "Michael S. Tsirkin" <mst@redhat.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: Cedric Le Goater <clg@fr.ibm.com>,
qemu-devel@nongnu.org, Anthony Liguori <aliguori@amazon.com>,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio-pci: enable bus master for old guests
Date: Thu, 11 Sep 2014 20:50:13 +0300 [thread overview]
Message-ID: <20140911175013.GA29028@redhat.com> (raw)
In-Reply-To: <20140911174701.GB27774@redhat.com>
On Thu, Sep 11, 2014 at 08:47:01PM +0300, Michael S. Tsirkin wrote:
> On Thu, Sep 11, 2014 at 06:45:33PM +0200, Greg Kurz wrote:
> > From: Michael S. Tsirkin <mst@redhat.com>
> >
> > commit cc943c36faa192cd4b32af8fe5edb31894017d35
> > pci: Use bus master address space for delivering MSI/MSI-X messages
> > breaks virtio-net for rhel6.[56] x86 guests because they don't
> > enable bus mastering for virtio PCI devices. For the same reason,
> > rhel6.[56] ppc64 guests cannot boot on a virtio-blk disk anymore.
> >
> > Old guests forgot to enable bus mastering, enable it automatically on
> > DRIVER (ppc64 guests may never reach DRIVER_OK). We also need to prevent
> > these old guests to disable bus mastering (this happens when the driver
> > probes the device). And we must also re-enable bus mastering after migration.
> >
> > Cc: qemu-stable@nongnu.org
> > Reported-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > [ old guest detection on DRIVER,
> > squashed patch from Michael S. Tsirkin to re-enable bus mastering,
> > Greg Kurz <gkurz@linux.vnet.ibm.com> ]
> > Tested-by: Cedric Le Goater <clg@fr.ibm.com>
> > Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
>
> I think this is too fragile. Let's try to figure out a strategy
> that does not depend on VIRTIO_PCI_FLAG_BUS_MASTER_BUG.
OTOH it does work, so I think I'll apply something similar (this one is
slightly broken wrt migration) and work on simplifications as a follow-up.
> > ---
> > hw/virtio/virtio-pci.c | 18 +++++++++++++-----
> > 1 file changed, 13 insertions(+), 5 deletions(-)
> >
> > diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> > index ddb5da1..f981841 100644
> > --- a/hw/virtio/virtio-pci.c
> > +++ b/hw/virtio/virtio-pci.c
> > @@ -317,9 +317,11 @@ static void virtio_ioport_write(void *opaque, uint32_t addr, uint32_t val)
> > /* Linux before 2.6.34 sets the device as OK without enabling
> > the PCI device bus master bit. In this case we need to disable
> > some safety checks. */
> > - if ((val & VIRTIO_CONFIG_S_DRIVER_OK) &&
> > + if ((val & VIRTIO_CONFIG_S_DRIVER) &&
> > !(proxy->pci_dev.config[PCI_COMMAND] & PCI_COMMAND_MASTER)) {
> > proxy->flags |= VIRTIO_PCI_FLAG_BUS_MASTER_BUG;
> > + memory_region_set_enabled(&proxy->pci_dev.bus_master_enable_region,
> > + true);
> > }
> > break;
> > case VIRTIO_MSI_CONFIG_VECTOR:
> > @@ -473,10 +475,14 @@ static void virtio_write_config(PCIDevice *pci_dev, uint32_t address,
> > pci_default_write_config(pci_dev, address, val, len);
> >
> > if (range_covers_byte(address, len, PCI_COMMAND) &&
> > - !(pci_dev->config[PCI_COMMAND] & PCI_COMMAND_MASTER) &&
> > - !(proxy->flags & VIRTIO_PCI_FLAG_BUS_MASTER_BUG)) {
> > - virtio_pci_stop_ioeventfd(proxy);
> > - virtio_set_status(vdev, vdev->status & ~VIRTIO_CONFIG_S_DRIVER_OK);
> > + !(pci_dev->config[PCI_COMMAND] & PCI_COMMAND_MASTER)) {
> > + if (proxy->flags & VIRTIO_PCI_FLAG_BUS_MASTER_BUG) {
> > + memory_region_set_enabled(&proxy->pci_dev.bus_master_enable_region,
> > + true);
> > + } else {
> > + virtio_pci_stop_ioeventfd(proxy);
> > + virtio_set_status(vdev, vdev->status & ~VIRTIO_CONFIG_S_DRIVER_OK);
> > + }
> > }
> > }
> >
> > @@ -890,6 +896,8 @@ static void virtio_pci_vmstate_change(DeviceState *d, bool running)
> > if ((vdev->status & VIRTIO_CONFIG_S_DRIVER_OK) &&
> > !(proxy->pci_dev.config[PCI_COMMAND] & PCI_COMMAND_MASTER)) {
> > proxy->flags |= VIRTIO_PCI_FLAG_BUS_MASTER_BUG;
> > + memory_region_set_enabled(&proxy->pci_dev.bus_master_enable_region,
> > + true);
> > }
> > virtio_pci_start_ioeventfd(proxy);
> > } else {
next prev parent reply other threads:[~2014-09-11 17:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 16:45 [Qemu-devel] [PATCH] virtio-pci: enable bus master for old guests Greg Kurz
2014-09-11 17:47 ` Michael S. Tsirkin
2014-09-11 17:50 ` Michael S. Tsirkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-08 16:05 Michael S. Tsirkin
2014-09-08 16:26 ` Jan Kiszka
2014-09-08 16:35 ` Michael S. Tsirkin
2014-09-09 14:13 ` Michael Roth
2014-09-09 14:27 ` Michael S. Tsirkin
2014-09-09 22:35 ` Greg Kurz
2014-09-10 2:39 ` Alexey Kardashevskiy
2014-09-10 8:14 ` Nikunj A Dadhania
2014-09-10 8:58 ` Greg Kurz
2014-09-10 9:32 ` Michael S. Tsirkin
2014-09-10 9:01 ` Greg Kurz
2014-09-10 9:18 ` Nikunj A Dadhania
2014-09-10 11:27 ` Michael S. Tsirkin
2014-09-10 9:15 ` Nikunj A Dadhania
2014-09-10 10:54 ` Michael S. Tsirkin
2014-09-10 9:26 ` 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=20140911175013.GA29028@redhat.com \
--to=mst@redhat.com \
--cc=aliguori@amazon.com \
--cc=clg@fr.ibm.com \
--cc=gkurz@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).