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:
VIRTIO-134: Make it clear how chained indirect descriptors must work.
--------------------------------------
Chained indirect descriptors were partially banned by virtio-15, which said how devices would handle them (by terminating the descriptor when it hits the end of the indirect descriptors). It didn't spell out that (obviously) they shouldn't be generated by drivers!
It also leaves open the possibility of one or more direct descriptors followed by a trailing indirect descriptor. All implementations I know of handle this, though none I know of generate such things. My test lguest implementation didn't (now fixed); we should spell out explicitly that it's possible.
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio/201502/msg00043.html
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio 1.0 cs03", 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.
-------------------------------------- |
