summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2014-03-02 21:34:28 +0000
committermstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2014-03-02 21:34:28 +0000
commitf0b00693e76a3d90028c337e9f5546ab949c2ca3 (patch)
tree2cba106c3b2cd86ff2b9e1163e66c9caab44b7db
parent61e96946bb276abd485cf4f605f9f8a6efc3e005 (diff)
Legacy Interface: Device Configuration Space
Change accepted on VIRTIO TC Meeting, 3 December 2013 legacy has no generation field. add SHOULD statement to document multi-byte field access rules. Signed-off-by: Michael S. Tsirkin <mst@redhat.com> git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@290 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
-rw-r--r--content.tex6
1 files changed, 5 insertions, 1 deletions
diff --git a/content.tex b/content.tex
index 744ba34..cc0f363 100644
--- a/content.tex
+++ b/content.tex
@@ -236,7 +236,11 @@ The correct endian-ness is documented explicitly for each device.
Legacy devices did not have a configuration generation field, thus are
susceptible to race conditions if configuration is updated. This
-effects the block capacity and network mac fields; best practice is to
+effects the block \field{capacity} (see \ref{sec:Device Types /
+Block Device / Feature bits / Device configuration layout}) and
+network \field{mac} (see \ref{sec:Device Types / Network Device /
+Device configuration layout}) fields;
+when using the legacy interface, drivers SHOULD
read these fields multiple times until two reads generate a consistent
result.