From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, groug@kaod.org
Cc: qemu-devel@nongnu.org, cornelia.huck@de.ibm.com,
marcel@redhat.com, vkaplans@redhat.com, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 2/2] virtio-pci: Disable modern interface if backend without VIRTIO_F_VERSION_1
Date: Fri, 9 Sep 2016 19:56:46 +0200 [thread overview]
Message-ID: <8e992b2a-26a4-d21d-a77f-c7c2e7257da3@redhat.com> (raw)
In-Reply-To: <20160909204823-mutt-send-email-mst@kernel.org>
On 09/09/2016 07:48 PM, Michael S. Tsirkin wrote:
> On Fri, Sep 09, 2016 at 03:10:07PM +0200, Maxime Coquelin wrote:
>> This patch makes pci devices plugging more robust, by not confusing
>> guest with modern interface when the backend doesn't support
>> VIRTIO_F_VERSION_1.
>>
>> Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
>> Cc: Marcel Apfelbaum <marcel@redhat.com>
>> Cc: Michael S. Tsirkin <mst@redhat.com>
>> Cc: qemu-stable@nongnu.org
>> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>> ---
>> hw/virtio/virtio-pci.c | 15 +++++++++++++++
>> hw/virtio/virtio-pci.h | 5 +++++
>> 2 files changed, 20 insertions(+)
>>
>> diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
>> index 755f921..9e88d7b 100644
>> --- a/hw/virtio/virtio-pci.c
>> +++ b/hw/virtio/virtio-pci.c
>> @@ -1581,6 +1581,21 @@ static void virtio_pci_device_plugged(DeviceState *d, Error **errp)
>> uint32_t size;
>> VirtIODevice *vdev = virtio_bus_get_device(&proxy->bus);
>>
>> + /*
>> + * Virtio capabilities present without
>> + * VIRTIO_F_VERSION_1 confuses guests
>> + */
>> + if (!virtio_test_backend_virtio_1(vdev, errp)) {
>> + virtio_pci_disable_modern(proxy);
>> + }
>> +
>> + legacy = virtio_pci_legacy(proxy);
>> + modern = virtio_pci_modern(proxy);
>> + if (!legacy && !modern) {
>> + error_setg(errp, "PCI device is neither legacy nor modern.");
>> + return;
>> + }
>> +
>
> How does this interact with
> virtio-pci: error out when both legacy and modern modes are disabled
> ?
> If it's the same, I'd rather pick that one and apply your
> change on top.
Not exactly, since with my patch modern can be disabled after realize
callback has been called.
But I will base my next revision on top of Greg's patch,
and use the same pattern as he did use.
Thanks,
Maxime
prev parent reply other threads:[~2016-09-09 17:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 13:10 [Qemu-devel] [PATCH v2 0/2] virtio-pci: Improve device plugging whith legacy backends Maxime Coquelin
2016-09-09 13:10 ` [Qemu-devel] [PATCH v2 1/2] virtio: Add function to check whether backend supports VIRTIO_1 Maxime Coquelin
2016-09-09 17:00 ` Marcel Apfelbaum
2016-09-09 17:47 ` Michael S. Tsirkin
2016-09-09 17:49 ` Maxime Coquelin
2016-09-11 8:04 ` Marcel Apfelbaum
2016-09-12 12:28 ` Cornelia Huck
2016-09-12 16:42 ` Maxime Coquelin
2016-09-12 16:54 ` Michael S. Tsirkin
2016-09-09 13:10 ` [Qemu-devel] [PATCH v2 2/2] virtio-pci: Disable modern interface if backend without VIRTIO_F_VERSION_1 Maxime Coquelin
2016-09-09 17:04 ` Marcel Apfelbaum
2016-09-09 17:48 ` Michael S. Tsirkin
2016-09-09 17:56 ` Maxime Coquelin [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=8e992b2a-26a4-d21d-a77f-c7c2e7257da3@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=groug@kaod.org \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=vkaplans@redhat.com \
/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).