qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] virtio-pci: error out when both legacy and modern modes are disabled
Date: Thu, 21 Jul 2016 19:02:39 +0200	[thread overview]
Message-ID: <20160721190239.0153576f@bahia.lan> (raw)
In-Reply-To: <5790FDCC.2010509@gmail.com>

On Thu, 21 Jul 2016 19:52:28 +0300
Marcel Apfelbaum <marcel.apfelbaum@gmail.com> wrote:

> On 07/21/2016 06:52 PM, Greg Kurz wrote:
> > From: Greg Kurz <gkurz@linux.vnet.ibm.com>
> >
> > Without presuming if we got there because of a user mistake or some
> > more subtle bug in the tooling, it really does not make sense to
> > implement a non-functional device.
> >
> > Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> > v2: - error out at realize time as suggested by Connie
> >      - updated title and changelog
> > ---
> >   hw/virtio/virtio-pci.c |    6 ++++++
> >   1 file changed, 6 insertions(+)
> >
> > diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> > index f0677b73d860..8d707aac0c21 100644
> > --- a/hw/virtio/virtio-pci.c
> > +++ b/hw/virtio/virtio-pci.c
> > @@ -1838,6 +1838,12 @@ static void virtio_pci_dc_realize(DeviceState *qdev, Error **errp)
> >       VirtIOPCIProxy *proxy = VIRTIO_PCI(qdev);
> >       PCIDevice *pci_dev = &proxy->pci_dev;
> >
> > +    if (proxy->flags & VIRTIO_PCI_FLAG_DISABLE_LEGACY &&
> > +        proxy->flags & VIRTIO_PCI_FLAG_DISABLE_MODERN) {
> > +        error_setg(errp, "device is unserviceable when both legacy and modern modes are disabled. At least one of the disable-modern or disable-legacy properties should be set to false.");
> > +        return;
> > +    }
> > +  
> 
> Hi Greg,
> 
> I agree with the patch, but other patch in the mailing list
> replaces the flags with standalone fields:
> 
> https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg04744.html
> 

v3 will be using virtio_pci_legacy() and virtio_pci_modern().

> Also the error line may be too long and need to be truncated.
> 

I'll rephrase the message. BTW is there a formal limit for the length
of error lines ? 80 chars ?

> Thanks,
> Marcel
> 
> >       if (!(proxy->flags & VIRTIO_PCI_FLAG_DISABLE_PCIE) &&
> >           !(proxy->flags & VIRTIO_PCI_FLAG_DISABLE_MODERN)) {
> >           pci_dev->cap_present |= QEMU_PCI_CAP_EXPRESS;
> >
> >  
> 

  reply	other threads:[~2016-07-21 17:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 15:52 [Qemu-devel] [PATCH v2] virtio-pci: error out when both legacy and modern modes are disabled Greg Kurz
2016-07-21 16:52 ` Marcel Apfelbaum
2016-07-21 17:02   ` Greg Kurz [this message]
2016-07-21 17:06     ` Greg Kurz
2016-07-21 20:00 ` Eric Blake
  -- strict thread matches above, loose matches on Subject: below --
2016-09-09  9:00 Greg Kurz

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=20160721190239.0153576f@bahia.lan \
    --to=groug@kaod.org \
    --cc=cornelia.huck@de.ibm.com \
    --cc=marcel.apfelbaum@gmail.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).