From: Jason Wang <jasowang@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH V2 1/2] virtio: introduce virtqueue state as basic facility
Date: Thu, 25 Mar 2021 10:38:36 +0800 [thread overview]
Message-ID: <96f9de37-d3cb-e861-db4e-b2adf9738b89@redhat.com> (raw)
In-Reply-To: <YFsH9/VKi5mr0Ssc@stefanha-x1.localdomain>
在 2021/3/24 下午5:35, Stefan Hajnoczi 写道:
> On Wed, Mar 24, 2021 at 04:15:55PM +0800, Jason Wang wrote:
>> 在 2021/3/23 下午6:27, Stefan Hajnoczi 写道:
>>> On Mon, Mar 22, 2021 at 11:47:16AM +0800, Jason Wang wrote:
>>>> +
>>>> +\devicenormative{\subsection}{Virtqueue State}{Basic Facilities of a Virtio Device / Virtqueue State}
>>>> +
>>>> +If VIRTIO_F_QUEUE_STATE has been negotiated, a device MUST NOT clear
>>>> +the queue state upon reset and MUST reset the queue state when the
>>>> +driver sets ACKNOWLEDGE status bit.
>>> I only see normative sections mentioning getting the virtqueue state but
>>> not setting it. Please explain how setting works.
>>
>> You mean the device normative part? I think the description of avail state
>> and used state can explain itself. Or I miss something?
> Oops, I missed the earlier normative section that says the driver must
> set the virtqueue state after FEATURES_OK but before DRIVER_OK.
>
> When re-reading I noticed that there is a typo: s/FEATURE_OK/FEATURES_OK/.
Will fix.
Thanks
>
> Stefan
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2021-03-25 2:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 3:47 [virtio-comment] [PATCH V2 0/2] Introduce VIRTIO_F_QUEUE_STATE Jason Wang
2021-03-22 3:47 ` [virtio-comment] [PATCH V2 1/2] virtio: introduce virtqueue state as basic facility Jason Wang
2021-03-22 8:19 ` [virtio-comment] " Eugenio Perez Martin
2021-03-23 2:54 ` Jason Wang
2021-03-23 9:27 ` Eugenio Perez Martin
2021-03-23 10:27 ` [virtio-comment] " Stefan Hajnoczi
2021-03-24 8:15 ` Jason Wang
2021-03-24 9:35 ` Stefan Hajnoczi
2021-03-25 2:38 ` Jason Wang [this message]
2021-03-24 9:38 ` Stefan Hajnoczi
2021-03-25 2:42 ` Jason Wang
2021-03-25 9:59 ` Stefan Hajnoczi
2021-03-22 3:47 ` [virtio-comment] [PATCH V2 2/2] virtio-pci: implement VIRTIO_F_QUEUE_STATE Jason Wang
2021-03-23 10:02 ` Stefan Hajnoczi
2021-03-23 10:40 ` [virtio-comment] [PATCH V2 0/2] Introduce VIRTIO_F_QUEUE_STATE Stefan Hajnoczi
2021-03-24 7:05 ` Jason Wang
2021-03-24 10:05 ` Stefan Hajnoczi
2021-03-25 2:57 ` Jason Wang
2021-03-25 10:03 ` [virtio-comment] [PATCH V2 0/2] Introduce VIRTIO_F_QUEUE_STATE\\ 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=96f9de37-d3cb-e861-db4e-b2adf9738b89@redhat.com \
--to=jasowang@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.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