|
Should the TC accept changes listed in the description to resolve issue 169,
for inclusion in specification version(s) "virtio-v1.3-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 #169: improve PCIx msix register description
--------------------------------------
Problem:
Current wording queue_msix_vector and config_msix_vector says "for MSI-X", which is bit confusing.
Solution:
config_msix_vector and queue_msix_vector are the msix vector number for configuration change and queue related interrupts.
Patch for vote: https://lists.oasis-open.org/archives/virtio-comment/202304/msg00436.html
Patch link for maintainers automation: https://lore.kernel.org/virtio-comment/20230421145434.83774-1-parav@nvidia.com/
(contains reviewed-by, ack by signatures).
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-comment/202304/msg00436.html
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio-v1.3-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.
--------------------------------------
|
