OASIS Virtual I/O Device (VIRTIO) TC Public Documents

Number of Documents Show last documents per workgroup
Document Descriptions
OASIS Virtual I/O Device (VIRTIO) TC   (Showing 10 of 207)
Document Name # Size State Submitter Date Action
0
14K
Draft
Michael S. Tsirkin
2020-05-07
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 #76: Cross-device resource sharing -------------------------------------- This patch defines a UUID-based mechanism for sharing objects between different virtio devices, and it adds a new virtio-gpu command for exporting virtio-gpu resources. The latest patch: https://lists.oasis-open.org/archives/virtio-comment/202003/msg00035.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202003/msg00035.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. --------------------------------------
0
15K
Draft
Michael S. Tsirkin
2020-05-07
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 #54: Add virtio sound device specification -------------------------------------- Add base specification for virtio-snd (device 25). https://lists.oasis-open.org/archives/virtio-dev/202003/msg00185.html - RFC: https://lists.oasis-open.org/archives/virtio-dev/201908/msg00078.html - v1: https://lists.oasis-open.org/archives/virtio-dev/201909/msg00130.html - v2: https://lists.oasis-open.org/archives/virtio-dev/201911/msg00010.html - v3: https://lists.oasis-open.org/archives/virtio-dev/201912/msg00088.html - v4: https://lists.oasis-open.org/archives/virtio-dev/202001/msg00028.html - v5: https://lists.oasis-open.org/archives/virtio-dev/202001/msg00059.html - v6: https://lists.oasis-open.org/archives/virtio-dev/202003/msg00045.html - v7: https://lists.oasis-open.org/archives/virtio-dev/202003/msg00098.html - v8 (latest): https://lists.oasis-open.org/archives/virtio-dev/202003/msg00185.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- - v8 (latest): https://lists.oasis-open.org/archives/virtio-dev/202003/msg00185.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. --------------------------------------
0
14K
Draft
Michael S. Tsirkin
2020-05-03
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 #74: content: reserve device ID 32 for SCMI device -------------------------------------- virtio-scmi provides a simple transport for the Arm SCMI (*S*ystem *C*ontrol and *M*anagement *I*nterface) protocol. [This patch requests device ID 32](https://lists.oasis-open.org/archives/virtio-comment/202003/msg00012.html), as device ID 31 has been requested for virtio-video (#67). There is also patch for the device itself ([PATCH v3] [Add virtio SCMI device specification](https://lists.oasis-open.org/archives/virtio-comment/202003/msg00033.html)). -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202003/msg00012.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. --------------------------------------
0
15K
Draft
Michael S. Tsirkin
2020-04-07
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 #74: content: reserve device ID 32 for SCMI device -------------------------------------- virtio-scmi provides a simple transport for the Arm SCMI (*S*ystem *C*ontrol and *M*anagement *I*nterface) protocol ([patch v2](https://lists.oasis-open.org/archives/virtio-comment/202002/msg00069.html)). [This patch](https://lists.oasis-open.org/archives/virtio-comment/202003/msg00012.html) requests device ID 32, as device ID 31 has been requested for virtio-video (#67). -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202002/msg00069.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. --------------------------------------
0
13K
Draft
Michael S. Tsirkin
2020-03-23
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 #68: content: reserve device ID for mac80211_hwsim -------------------------------------- As described in the patch, we'd like to have a device ID for Linux's hwsim to allow multiple VMs to participate in a simulated wireless network. https://lists.oasis-open.org/archives/virtio-comment/201911/msg00051.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/201911/msg00051.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. --------------------------------------
0
14K
Draft
Michael S. Tsirkin
2020-03-23
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 #67: content: reserve device IDs for video encoder and decoder device -------------------------------------- The virtio-video protocol is for video encoder and decoder. ([RFCv1], [v2]) It needs two device IDs for decoder and encoder respectively. We requested 30 and 31 in [this patch](https://markmail.org/thread/bzfqdwk47pecnsah), as 29 had been requested for [hwsim wireless simulation](https://markmail.org/message/q6qdl4zoycpkg3w5). https://lists.oasis-open.org/archives/virtio-comment/201912/msg00031.html [RFCv1]: https://markmail.org/thread/gtip3dil4gwr3qan [v2]: https://markmail.org/thread/4ufu3l3mwyoojxjb -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/201912/msg00031.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. --------------------------------------
0
16K
Draft
Michael S. Tsirkin
2020-03-18
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 #73: virtio-net: Add support for the flexible driver notification structure -------------------------------------- Currently, the driver notification (available buffer notification) has a fixed structure. If VIRTIO_F_NOTIFICATION_DATA has been negotiated, it includes: vqn, next_off and next_wrap. If notify_off_multiplier > 0, the VQ number can be derived by the device from the Queue Notify address, so vqn may be redundant. Some devices benefit from receiving an additional data with driver notifications. This data can optionally replace the vqn field in the driver notification structure. The latest patch: [https://lists.oasis-open.org/archives/virtio-comment/202003/msg00019.html](https://lists.oasis-open.org/archives/virtio-comment/202003/msg00019.html) -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202003/msg00019.html](https://lists.oasis-open.org/archives/virtio-comment/202003/msg00019.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. --------------------------------------
0
13K
Draft
Michael S. Tsirkin
2020-03-10
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 #72: virtio-net: Fix VIRTIO_NET_F_GUEST_HDRLEN feature definition -------------------------------------- Fix driver and device requirements with regards to the VIRTIO_NET_F_GUEST_HDRLEN feature - 'hdr_len' must be accurate only for TSO/UFO packets. -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202002/msg00053.html](https://lists.oasis-open.org/archives/virtio-comment/202002/msg00053.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. --------------------------------------
0
14K
Draft
Michael S. Tsirkin
2020-03-09
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 #56: split-ring: Demand that a device must not change descriptor entries -------------------------------------- So far the spec only indirectly says that a descriptor table entry is not modified by a device when processing it. Make this explicit by adding it as normative requirement. Existing drivers already depend on this. Patch: https://lists.oasis-open.org/archives/virtio-dev/201911/msg00040.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-dev/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. --------------------------------------
0
14K
Draft
Michael S. Tsirkin
2020-03-05
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 #66: virtio-net: Define possibility to deliver per-packet hash -------------------------------------- Feature VIRTIO_NET_F_HASH_REPORT indicates the device is able to deliver per-packet hash. If negotiated, this extends packet structure to include calculated hash value and hash type, In this case the device also supports commands for configuration of enabled hashes and a key for hash calculation. https://lists.oasis-open.org/archives/virtio-comment/202002/msg00034.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202002/msg00034.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. --------------------------------------