From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH] virtio-pci: fix queue_enable write
Date: Wed, 10 Jun 2020 00:16:29 -0400 [thread overview]
Message-ID: <20200610001608-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <a6ad8f9d-8613-16f8-f811-7ef2824c5f35@redhat.com>
On Wed, Jun 10, 2020 at 10:03:28AM +0800, Jason Wang wrote:
>
> On 2020/6/9 下午11:43, Michael S. Tsirkin wrote:
> > On Fri, May 29, 2020 at 11:07:28AM +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 sepc, we should not
> > spec?
>
>
> Chapter 4.1.4.3.2 said:
>
> "
>
> The driver MUST NOT write a 0 to queue_enable.
>
> "
>
I mean you misspelled spec as sepc :)
> >
> > > assume that the value is 1.
> > >
> > > Fix this by ignoring the write value other than 1.
> > >
> > > Cc: Michael S. Tsirkin <mst@redhat.com>
> > > Cc: Stefan Hajnoczi <stefanha@redhat.com>
> > > Signed-off-by: Jason Wang <jasowang@redhat.com>
> >
> > Do we want to call virtio_error here so we can figure out something's wrong?
>
>
> That looks better. Will do.
>
> Thanks
>
>
> >
> >
> >
> > > ---
> > > hw/virtio/virtio-pci.c | 10 ++++++----
> > > 1 file changed, 6 insertions(+), 4 deletions(-)
> > >
> > > diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> > > index d028c17c24..b3558eeaee 100644
> > > --- a/hw/virtio/virtio-pci.c
> > > +++ b/hw/virtio/virtio-pci.c
> > > @@ -1273,16 +1273,18 @@ 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) {
> > > + 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;
> > > + }
> > > 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 4:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 3:07 [PATCH] virtio-pci: fix queue_enable write Jason Wang
2020-05-29 13:00 ` Stefan Hajnoczi
2020-06-09 15:43 ` Michael S. Tsirkin
2020-06-10 2:03 ` Jason Wang
2020-06-10 4:16 ` Michael S. Tsirkin [this message]
2020-06-10 5:36 ` Jason Wang
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=20200610001608-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).