|
Should the TC accept changes listed in the description to resolve issue 36,
for inclusion in specification version(s) "virtio-v1.2-cs01", and future versions of the specification?
Please vote Yes if you agree with all of the following.
If you disagree, please vote No.
If you don't have an opinion, please vote Abstain.
I move that:
The TC agrees to resolve the following specification issue:
Issue #36: virtio ring features: inconsistent naming
--------------------------------------
Reported-by: Don Wallwork <don.wallwork@broadcom.com>
features like VIRTIO_F_EVENT_IDX and
VIRTIO_F_INDIRECT_DESC do not
appear in Linux kernel or QEMU code; VIRTIO_RING_F_EVENT_IDX and
VIRTIO_RING_F_INDIRECT_DESC
are used instead.
Also noticed that there seems to be an inconsistency in the spec in that
VIRTIO_F_EVENT_IDX is
used in some places and VIRTIO_F_RING_EVENT_IDX is used in others
https://lists.oasis-open.org/archives/virtio-comment/201902/msg00032.html
Proposed patch: https://lists.oasis-open.org/archives/virtio-comment/202105/msg00003.html
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-comment/202105/msg00003.html
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio-v1.2-cs01", and future versions of the
specification.
--------------------------------------
Reminder: A Voting Member must be active in a TC to maintain voting rights. As
the Virtio TC has adopted a standing rule to conduct business only by
electronic ballot, without Meetings, a Voting Member who fails to cast a ballot
in two consecutive Work Product Ballots loses his or her voting rights at the
close of the second ballot missed.
--------------------------------------
|
