|
Should the TC accept changes listed in the description to resolve issue 118,
for inclusion in specification version(s) "virtio-v1.2-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 #118: virtio-mem: VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE and interaction with memory properties
--------------------------------------
Looking into supporting virtio-mem
a) without a shared zeropage for the memory backing of the device -- not allowing the driver to read unplugged memory
b) on architectures with memory properties for RAM (e.g., s390x with storage keys and storage attributes)
requires extension of the spec to handle both cases cleanly and describe the expected semantics.
Let's specify VIRTIO_MEM_F_UNPLUGGED_INACCESSIBLE behaviour and expected interaction with memory properties, along some cleanups.
Latest proposal: https://lists.oasis-open.org/archives/virtio-comment/202109/msg00027.html
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-comment/202109/msg00027.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.
--------------------------------------
|
