From: Jason Wang <jasowang@redhat.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH V3 6/6] virtio-pci: unbreak queue_enable read
Date: Tue, 10 Nov 2015 10:51:21 +0800 [thread overview]
Message-ID: <56415BA9.2060107@redhat.com> (raw)
In-Reply-To: <20151109141446.183a3016.cornelia.huck@de.ibm.com>
On 11/09/2015 09:14 PM, Cornelia Huck wrote:
> On Fri, 6 Nov 2015 16:02:49 +0800
> Jason Wang <jasowang@redhat.com> wrote:
>
>> Guest always get zero when reading queue_enable. This violates
>> spec. Fixing this by setting the queue_enable to true during any guest
>> writing and setting it to zero during reset.
>>
>> Cc: Michael S. Tsirkin <mst@redhat.com>
>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>> ---
>> hw/virtio/virtio-pci.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
>> index e4449da..52a9e33 100644
>> --- a/hw/virtio/virtio-pci.c
>> +++ b/hw/virtio/virtio-pci.c
>> @@ -1384,6 +1384,7 @@ static void virtio_pci_common_write(void *opaque, hwaddr addr,
>> proxy->vqs[vdev->queue_sel].avail[0],
>> ((uint64_t)proxy->vqs[vdev->queue_sel].used[1]) << 32 |
>> proxy->vqs[vdev->queue_sel].used[0]);
>> + proxy->vqs[vdev->queue_sel].enabled = 1;
> Hm. Spec says that the driver MUST NOT write 0 here.
Yes.
> Does this need a
> check?
Add warn in this case? I'm not sure, I read the spec as "writing any
value implies enabling". (And the patch itself does not conflict the spec).
>
> <Also, I think you can remove the 'TODO' comment - this should be
> handled now.>
Yes
>
>> break;
>> case VIRTIO_PCI_COMMON_Q_DESCLO:
>> proxy->vqs[vdev->queue_sel].desc[0] = val;
>> @@ -1831,9 +1832,15 @@ static void virtio_pci_reset(DeviceState *qdev)
>> {
>> VirtIOPCIProxy *proxy = VIRTIO_PCI(qdev);
>> VirtioBusState *bus = VIRTIO_BUS(&proxy->bus);
>> + int i;
>> +
>> virtio_pci_stop_ioeventfd(proxy);
>> virtio_bus_reset(bus);
>> msix_unuse_all_vectors(&proxy->pci_dev);
>> +
>> + for (i = 0; i < VIRTIO_QUEUE_MAX; i++) {
>> + proxy->vqs[i].enabled = 0;
>> + }
>> }
>>
>> static Property virtio_pci_properties[] = {
> Otherwise, this looks good to me.
>
>
Thanks
prev parent reply other threads:[~2015-11-10 2:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 8:02 [Qemu-devel] [PATCH V3 0/6] virtio 1.0 pci optimizations and fixes Jason Wang
2015-11-06 8:02 ` [Qemu-devel] [PATCH V3 1/6] virtio-pci: fix 1.0 virtqueue migration Jason Wang
2015-11-09 12:56 ` Cornelia Huck
2015-11-10 2:35 ` Jason Wang
2015-11-06 8:02 ` [Qemu-devel] [PATCH V3 2/6] memory: don't try to adjust endianness for zero length eventfd Jason Wang
2015-11-06 8:02 ` [Qemu-devel] [PATCH V3 3/6] KVM: add support for any length io eventfd Jason Wang
2015-11-11 11:01 ` Paolo Bonzini
2015-11-06 8:02 ` [Qemu-devel] [PATCH V3 4/6] virtio-pci: use zero length mmio eventfd for 1.0 notification cap when possible Jason Wang
2015-11-06 8:02 ` [Qemu-devel] [PATCH V3 5/6] virtio-pci: introduce pio notification capability for modern device Jason Wang
2015-11-06 8:02 ` [Qemu-devel] [PATCH V3 6/6] virtio-pci: unbreak queue_enable read Jason Wang
2015-11-09 13:14 ` Cornelia Huck
2015-11-10 2:51 ` Jason Wang [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=56415BA9.2060107@redhat.com \
--to=jasowang@redhat.com \
--cc=cornelia.huck@de.ibm.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).