|
Should the TC accept changes listed in the description to resolve issue VIRTIO-132,
for inclusion in specification version(s) "virtio 1.1 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:
VIRTIO-132: ccw: handling of more than 64 virtqueues
--------------------------------------
For virtio-ccw devices using classic queue indicators, we cannot handle devices with more than 64 queues as the indicator value is a 64 bit integer and we would not be able to notify for the higher number virtqueues. The driver needs to use two-stage indicators if a device has more than 64 virtqueues.
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
Make setting up classic queue indicators fail if the device has been configured for more than 64 virtqueues.
Proposed patch: https://www.oasis-open.org/apps/org/workgroup/virtio/email/archives/201702/msg00005.html
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio 1.1 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.
--------------------------------------
|
