Ballot Details: Resolve Issue #91: virtio-mem: minor clarification regarding read-access to unplugged blocks (CLOSED)

Ballot Question Should the TC accept changes listed in the description to resolve issue 91, for inclusion in specification version(s) "virtio-v1.2-cs01", and future versions of the specification?
Ballot Description 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 #91: virtio-mem: minor clarification regarding read-access to unplugged blocks
--------------------------------------
Let's clarify that we don't expect all DMA to work with unplugged blocks.
We really only give guarantees when reading from unplugged memory blocks
via the CPU, e.g., as done by Linux when creating a system dump via
kdump: the new kernel will copy the content of the old (crashed) kernel
via the CPU to user space, from where it will find its final destination
inside the dump file. Note that dumping via makedumpfile under Linux will
avoid reading unplugged blocks completely.

This is a preparation for device passthrough to VMs, whereby such
dedicated devices might not be able to read from unplugged memory blocks.

Proposed patch: https://lists.oasis-open.org/archives/virtio-comment/202011/msg00023.html
--------------------------------------

The TC accepts the following proposed changes to the specification:
--------------------------------------
https://lists.oasis-open.org/archives/virtio-comment/202011/msg00023.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.

--------------------------------------
Ballot Options
VOTING CLOSED: Monday, 14 December 2020 @ 8:15 am EST
Yes 5 100
No 0 0
Abstain 1
Open Date Monday, 7 December 2020 @ 8:15 am EST
Close Date Monday, 14 December 2020 @ 8:15 am EST
Ballot Type Official, as defined by organization policies and procedures

Voting Statistics

Number of votes cast (excluding abstentions) 5
Eligible members who have voted 6 of 8 75%
Eligible members who have not voted 2 of 8 25%

Voting Summary by Option

Options with highest number of votes are bold
Option # Votes % of Total
Yes 5 100%
No 0 0%
Abstain 1

Voting Details

Voter Name Company Vote * Time (UTC) Comments
* Carabas, Mihai Oracle Yes 2020-12-08 20:48:00
* Huck, Cornelia Red Hat Yes 2020-12-10 10:23:00
* Kiszka, Jan Siemens AG Yes 2020-12-12 14:27:00
* Moell, Matti OpenSynergy GmbH Yes 2020-12-07 13:40:00
* Pasic, Halil IBM Yes 2020-12-07 18:38:00
* Granata, Enrico Google Inc. Abstain 2020-12-07 16:44:00
* Hajnoczi, Stefan Red Hat --
* Tsirkin, Michael S. Red Hat --