qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Stefano Garzarella <sgarzare@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [PATCH V2] virtio-pci: fix queue_enable write
Date: Thu, 11 Jun 2020 11:05:35 +0800	[thread overview]
Message-ID: <03fafc96-cefc-a086-b82f-cd87730d9d98@redhat.com> (raw)
In-Reply-To: <20200610095224.2q4ivledb42ubsz4@steredhat>


On 2020/6/10 下午5:52, Stefano Garzarella wrote:
> On Wed, Jun 10, 2020 at 05:42:54AM -0400, Michael S. Tsirkin wrote:
>> 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
> I was confused by "The driver MUST NOT write a 0 to queue_enable.",
> interpreting it as "can write anything other than 0".


Yes, the spec is unclear about what happens if we write a value other 
than 0 or 1.

Maybe we should clarify that only 1 is allowed. Or writing value other 
than 1 may cause unexpected result.


>
> But as Jason also wrote in the commit message, the driver should write
> 1 to enable, so
>
> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>


Thanks


>
> Thanks,
> Stefano
>



  reply	other threads:[~2020-06-11  3:06 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
2020-06-10  9:52     ` Stefano Garzarella
2020-06-11  3:05       ` Jason Wang [this message]
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=03fafc96-cefc-a086-b82f-cd87730d9d98@redhat.com \
    --to=jasowang@redhat.com \
    --cc=mst@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 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).