From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [PATCH V2] virtio-pci: fix queue_enable write
Date: Wed, 10 Jun 2020 05:42:54 -0400 [thread overview]
Message-ID: <20200610054248-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200610085726.jerorykxbycoesyu@steredhat>
On Wed, Jun 10, 2020 at 10:57:26AM +0200, Stefano Garzarella wrote:
> On Wed, Jun 10, 2020 at 01:43:51PM +0800, Jason Wang wrote:
> > Spec said: The driver uses this to selectively prevent the device from
> > executing requests from this virtqueue. 1 - enabled; 0 - disabled.
> >
> > Though write 0 to queue_enable is forbidden by the spec, we should not
> > assume that the value is 1.
> >
> > Fix this by ignore the write value other than 1.
> >
> > Signed-off-by: Jason Wang <jasowang@redhat.com>
> > ---
> > Changes from V1:
> > - fix typo
> > - warn wrong value through virtio_error
> > ---
> > hw/virtio/virtio-pci.c | 12 ++++++++----
> > 1 file changed, 8 insertions(+), 4 deletions(-)
> >
> > diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> > index d028c17c24..7bc8c1c056 100644
> > --- a/hw/virtio/virtio-pci.c
> > +++ b/hw/virtio/virtio-pci.c
> > @@ -1273,16 +1273,20 @@ static void virtio_pci_common_write(void *opaque, hwaddr addr,
> > virtio_queue_set_vector(vdev, vdev->queue_sel, val);
> > break;
> > case VIRTIO_PCI_COMMON_Q_ENABLE:
> > - virtio_queue_set_num(vdev, vdev->queue_sel,
> > - proxy->vqs[vdev->queue_sel].num);
> > - virtio_queue_set_rings(vdev, vdev->queue_sel,
> > + if (val == 1) {
>
> Does it have to be 1 or can it be any value other than 0?
>
> Thanks,
> Stefano
spec says 1
> > + virtio_queue_set_num(vdev, vdev->queue_sel,
> > + proxy->vqs[vdev->queue_sel].num);
> > + virtio_queue_set_rings(vdev, vdev->queue_sel,
> > ((uint64_t)proxy->vqs[vdev->queue_sel].desc[1]) << 32 |
> > proxy->vqs[vdev->queue_sel].desc[0],
> > ((uint64_t)proxy->vqs[vdev->queue_sel].avail[1]) << 32 |
> > 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;
> > + proxy->vqs[vdev->queue_sel].enabled = 1;
> > + } else {
> > + virtio_error(vdev, "wrong value for queue_enable %"PRIx64, val);
> > + }
> > break;
> > case VIRTIO_PCI_COMMON_Q_DESCLO:
> > proxy->vqs[vdev->queue_sel].desc[0] = val;
> > --
> > 2.20.1
> >
> >
next prev parent reply other threads:[~2020-06-10 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 5:43 [PATCH V2] virtio-pci: fix queue_enable write Jason Wang
2020-06-10 8:57 ` Stefano Garzarella
2020-06-10 9:42 ` Michael S. Tsirkin [this message]
2020-06-10 9:52 ` Stefano Garzarella
2020-06-11 3:05 ` Jason Wang
2020-06-11 8:41 ` Stefan Hajnoczi
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=20200610054248-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@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 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.