|
Should the TC accept changes listed in the description to resolve issue 55,
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 #55: Entropy device: 5.4.6.1 lists wrong requirement
--------------------------------------
5.4.6.1 says:
> The driver MUST NOT place driver-readable buffers into the queue.
It looks like it must be changed to
> The driver MUST NOT place device-readable buffers into the queue.
Rationale:
The point of Entropy device is that driver supplies a buffer, and device fills it, so the buffer must be
device-writeable and driver-readable.
Buffers that are device-readable (driver-writeable) cannot be used by device, so they must be forbidden.
Proposal (by mst): https://lists.oasis-open.org/archives/virtio-comment/201911/msg00040.html
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-comment/201911/msg00040.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.
--------------------------------------
|
