diff options
author | mstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2015-04-22 11:25:58 +0000 |
---|---|---|
committer | mstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2015-04-22 11:25:58 +0000 |
commit | 8aae5034956b183536aae59586541a783e78c4e4 (patch) | |
tree | f3aa51ae7938c161bb88bda2b3c318ac69591051 | |
parent | e0ce988563106c29a5d88219b92ee63eb79a8cc7 (diff) |
cl: document r508: VIRTIO-139
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio/branches/v1.0@514 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
-rw-r--r-- | cl-os.tex | 20 |
1 files changed, 20 insertions, 0 deletions
@@ -99,6 +99,26 @@ of a Virtio Device / Virtqueues / The Virtqueue Used Ring} and Virtqueue Used Ring}. } \\ \hline +508 & 22 Apr 2015 & Michael Tsirkin & {VIRTIO-139: +pci: missing documentation for dealing with 64 bit config fields + +pci spec says what width access to use for 32, 16 and 8 +bit fields, but does not explicitly say what to do for +32 bit fields. As we have text that says driver must +treat 64 bit accesses as non-atomic, this seems +to imply driver should always do two 32 bit wide accesses. + +Let's make this an explicit requirement, and require +devices to support this. + +See \ref{sec:Virtio Transport Options / Virtio Over PCI Bus / PCI +Device Layout}, \ref{drivernormative:Virtio Transport Options / +Virtio Over PCI Bus / PCI Device Layout}, +\ref{devicenormative:Virtio Transport Options / Virtio Over PCI +Bus / PCI Device Layout} and \ref{sec:Conformance / Driver +Conformance / PCI Driver Conformance}. + } \\ +\hline 510 & 22 Apr 2015 & Michael Tsirkin & {conformance: add VIRTIO-137 statement links |