|
Should the TC accept changes listed in the description to resolve issue 171,
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 #171: create a way to access one device through another
--------------------------------------
there are multiple reasons to desire such functionality.
For example, for SRIOV memory access is controlled by device
address, so accesses to hypervisor memory by device itself
are hard to set up.
Such accesses can be useful for:
- provisioning
- emulation of legacy virtio
- migration
and more.
Proposal: https://lore.kernel.org/virtio-comment/cover.1683301091.git.mst@redhat.com/
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lore.kernel.org/virtio-comment/cover.1683301091.git.mst@redhat.com/
--------------------------------------
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.
--------------------------------------
|
