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 #25: virtio: generalize io_barrier/platform_iommu -------------------------------------- it isn't always clear to everyone when should device set platform_iommu and when io_barrier. for example, some platforms need tricks like flushing cache and this is in practice already covered by platform_iommu. Let's rename platform_iommu to access_platform and make it clear that with this flag which memory can be accessed and at what address is platform specific, without this flag device acts same as CPU. On the other hand, io_barriers is a confusing name as it is not clear which operations are meant by an barrier - it is not really the io that is ordered. Rename it to order_platform. barriers is just one possible implementation of a driver used to order accesses. See more motivation here: https://lists.oasis-open.org/archives/virtio/201811/msg00013.html -------------------------------------- The TC accepts the following proposed changes to the specification: -------------------------------------- https://lists.oasis-open.org/archives/virtio/201811/msg00013.html -------------------------------------- The TC agrees to include the above change(s) in specification version(s) "virtio-v1.1-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. --------------------------------------