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:
Conditional on the TC approving unanimously the
proposed resolutions to outstanding ballots:
https://www.oasis-open.org/apps/org/workgroup/virtio/ballot.php?id=2771
https://www.oasis-open.org/apps/org/workgroup/virtio/ballot.php?id=2772
https://www.oasis-open.org/apps/org/workgroup/virtio/ballot.php?id=2773
https://www.oasis-open.org/apps/org/workgroup/virtio/ballot.php?id=2774
to resolve issues VIRTIO-130, VIRTIO-133, VIRTIO-135, VIRTIO-136
respectively.
The TC resolves that the following, previously and separately approved, changes to the specification are all Non-Material:
VIRTIO-129: legacy: clean up virtqueue layout definitions
Generalize ”Legacy Interfaces: A Note
on Virtqueue Layout” to allow for different
alignment requirements. Have pci and
ccw refer to that section for legacy devices.
Remove the double definition of virtqueue
alignment (which referred to legacy, but
was not tagged as such) from the ccw section.
See 2.4.2, 4.1.5.1.4.1 and 4.3.2.2.2.
VIRTIO-118: ccw: clarify basic channel commands
”Basic channel commands” seems to be
not as clear as it could, so let’s spell out
which channel commands we refer to. See
4.3.1.
VIRTIO-116: ccw: allow WRITE_STATUS to fail
We want to be able to fail setting a status
on the device (e.g. FEATURES_OK if the
device can’t work with the features negotiated).
The easiest way to do that is to
allow the device to fail the WRITE_STATUS command
by posting a command reject. See 4.3.2.3.
VIRTIO-135: virtio-ring: comment fixup
virtio_ring.h included with spec has this
text:
/* Support for avail_idx and used_idx fields */
it should really refer to avail_event
and used_event. See Appendix A.
VIRTIO-136: document idx field in virtqueue used ring
Section 2.4.8 The Virtqueue Used Ring
listed the idx field, but never documented
it. See 2.4.8.
The TC resolves to request a Special Majority Vote for the advancement of the draft
virtio-v1.0-wd03, with the above changes, with the addition of a changelog
listing the above changes, as a Committee Specification
virtio-v1.0-cs03.
Location of the specification draft with the above changes:
https://www.oasis-open.org/apps/org/workgroup/virtio/download.php/55300/virtio-1.0-wd03.zip
This archive includes the editable Tex sources,
specification in PDF and HTML formats, as well as
versions with changes since CS02 highlighted.
For convenience, specification in PDF format with above changes
highlighted is provided:
https://www.oasis-open.org/apps/org/workgroup/virtio/download.php/55301/virtio-1.0-wd03-diff.pdf
You can also use the "revision history" chapter to locate the changes more easily.
--------------------------------------
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.
-------------------------------------- |
