|
Should the TC accept changes listed in the description to resolve issue VIRTIO-145,
for inclusion in specification version(s) "virtio 1.0 cs04", 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:
VIRTIO-145: pci: configuration access capability rules are unclear
--------------------------------------
Specification merely says PCI config access capability
aliases a device BAR. This seems to allow config access to
legacy BAR (for transitional devices) but how should device
interpret such an access?
--------------------------------------
The TC accepts the following proposed changes to the specification:
--------------------------------------
The point of the configuration access capability is to enable
access to other capabilities. The intent never was to allow
writes to a random place within device BARs.
Limiting drivers simplifies devices - and devices can always
add another capability if drivers ever want to access
some other range.
http://article.gmane.org/gmane.comp.emulators.virtio.devel/877
--------------------------------------
The TC agrees to include the above change(s) in specification version(s) "virtio 1.0 cs04", 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.
--------------------------------------
|
