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 211)
Document Name # Size State Submitter Date Action
0
14K
Draft
Michael S. Tsirkin
2020-09-17
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 #84: virtio-balloon: Update spec to include features hinting, poison, and reporting -------------------------------------- Update the device specification for virtio-balloon to include recently added features hinting, poison, and reporting. Both the hinting and poison feature were added some time ago, but not documented. The page reporting Linux implementation is already upstream and was included in the 5.8 [kernel](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b0c504f154718904ae49349147e3b7e6ae91ffdc) and the [QEMU](https://lists.oasis-open.org/archives/virtio-dev/202004/msg00180.html) portion is already upstream. Latest posted proposal ("[PATCH v8 0/3] virtio-spec: Add documentation for recently added balloon features") can be found at: https://lists.oasis-open.org/archives/virtio-comment/202008/msg00054.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202008/msg00054.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-09-08
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 #84: virtio-balloon: Update spec to include features hinting, poison, and reporting -------------------------------------- Update the device specification for virtio-balloon to include recently added features hinting, poison, and reporting. Both the hinting and poison feature were added some time ago, but not documented. The page reporting Linux implementation is already upstream and was included in the 5.8 [kernel](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b0c504f154718904ae49349147e3b7e6ae91ffdc) and the [QEMU](https://lists.oasis-open.org/archives/virtio-dev/202004/msg00180.html) portion is already upstream. Latest posted proposal ("[PATCH v8 0/3] virtio-spec: Add documentation for recently added balloon features") can be found at: https://lists.oasis-open.org/archives/virtio-comment/202008/msg00054.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-dev/202004/msg00180.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-08-17
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 #81: content: Reserve virtio-nsm device ID -------------------------------------- The NitroSecureModule is a device with a very stripped down Trusted Platform Module functionality, which is used in the context of a Nitro Enclave (see https://lkml.org/lkml/2020/4/21/1020) to provide boot time measurement and attestation. Since this device provides some critical cryptographic operations, there are a series of operations which are required to have guarantees of atomicity, ordering and consistency: operations fully succeed or fully fail, including when some external events might interfere in the process: live migration, crashes, etc; any failure in the critical section requires termination of the enclave it is attached to, so the device needs to be as resilient as possible, simplicity is strongly desired. To account for that, the device and driver are made to have very few error cases in the critical path and the operations themselves can be rolled back and retried if events happen outside the critical area, while processing a request. The driver itself can be made very simple and thus is easily portable. Since the requests can be handled directly in the virtio queue, serving most requests requires no additional buffering or memory allocations on the host side. Patch link: https://lists.oasis-open.org/archives/virtio-comment/202005/msg00093.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202005/msg00093.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-07-27
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 #82: virtio-mem: add initial device specification -------------------------------------- Add the initial device specification for virtio-mem. The Linux implementation is in 5.8-rc1, the QEMU version is on its way upstream and should get merged soon. Latest posted proposal ("[PATCH v2 0/3] virtio-spec: Add virtio-mem device specification") can be found at https://lists.oasis-open.org/archives/virtio-comment/202006/msg00010.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio-comment/202006/msg00010.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-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. --------------------------------------