From: Greg Kurz <groug@kaod.org>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v4] virtio-pci: error out when both legacy and modern modes are disabled
Date: Fri, 22 Jul 2016 12:11:11 +0200 [thread overview]
Message-ID: <20160722121111.4626226f@bahia.lan> (raw)
In-Reply-To: <20160722100435.1cf57293.cornelia.huck@de.ibm.com>
On Fri, 22 Jul 2016 10:04:35 +0200
Cornelia Huck <cornelia.huck@de.ibm.com> wrote:
> On Thu, 21 Jul 2016 23:21:16 +0200
> Greg Kurz <groug@kaod.org> 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>
> > Reviewed-by: Marcel Apfelbaum <marcel@redhat.com>
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> > v4: - rephrased error message and provide a hint to the user
> > - split string literals to stay below 80 characters
> > - added Marcel's R-b tag
> > ---
> > hw/virtio/virtio-pci.c | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> > index 755f9218b77d..72c4b392ffda 100644
> > --- a/hw/virtio/virtio-pci.c
> > +++ b/hw/virtio/virtio-pci.c
> > @@ -1842,6 +1842,14 @@ static void virtio_pci_dc_realize(DeviceState *qdev, Error **errp)
> > VirtIOPCIProxy *proxy = VIRTIO_PCI(qdev);
> > PCIDevice *pci_dev = &proxy->pci_dev;
> >
> > + if (!(virtio_pci_modern(proxy) || virtio_pci_legacy(proxy))) {
>
> I'm not sure that I didn't mess up the sequence of the realize
> callbacks, but could disable_legacy still be AUTO here? In that case,
> we'd fail for disable-modern=on and disable-legacy unset (i.e., AUTO),
> which would be ok for pcie but not for !pcie.
>
Marcel made the same comment in:
https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg05225.html
If the user explicitly disables modern, she shouldn't rely on QEMU
implicitly enabling legacy, hence the suggestion in error_append_hint().
> > + error_setg(errp, "device cannot work when both modern and legacy modes"
> > + " are disabled");
> > + error_append_hint(errp, "Set either disable-modern or disable-legacy"
> > + " to off\n");
> > + return;
> > + }
> > +
> > if (!(proxy->flags & VIRTIO_PCI_FLAG_DISABLE_PCIE) &&
> > virtio_pci_modern(proxy)) {
> > pci_dev->cap_present |= QEMU_PCI_CAP_EXPRESS;
> >
>
next prev parent reply other threads:[~2016-07-22 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 21:21 [Qemu-devel] [PATCH v4] virtio-pci: error out when both legacy and modern modes are disabled Greg Kurz
2016-07-21 21:55 ` Greg Kurz
2016-07-22 7:51 ` Marcel Apfelbaum
2016-07-22 8:04 ` Cornelia Huck
2016-07-22 10:11 ` Greg Kurz [this message]
2016-07-22 10:32 ` Cornelia Huck
2016-07-22 13:23 ` Greg Kurz
2016-07-22 13:42 ` Cornelia Huck
2016-07-22 14: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=20160722121111.4626226f@bahia.lan \
--to=groug@kaod.org \
--cc=cornelia.huck@de.ibm.com \
--cc=eblake@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.