From 12e4378536ea473f578edf05b83c78b9f846d516 Mon Sep 17 00:00:00 2001
From: mstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>
Date: Wed, 29 Apr 2015 11:08:43 +0000
Subject: give explicit guidance on the use of 64 bit fields

Just saying 64 bit fields may not be atomic is true, but less helpful
than it might be.  Add explicit guidance about what the consequences of
non-atomicity are.

VIRTIO-140

Signed-off-by: James Bottomley <JBottomley@Odin.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio/branches/v1.0@520 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
---
 newdevice.tex | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'newdevice.tex')

diff --git a/newdevice.tex b/newdevice.tex
index c7e6221..28e1c7b 100644
--- a/newdevice.tex
+++ b/newdevice.tex
@@ -22,8 +22,9 @@ configuration information (the network device does this for filtering,
 otherwise the table in the config space could potentially be very
 large).
 
-Remember that configuration fields over 32 bits wide might not be
-atomically writable by the driver.
+Remember that configuration fields over 32 bits wide might not be atomically
+writable by the driver.  Therefore, no writeable field which triggers an
+action ought to be wider than 32 bits.
 
 \section{What Device Number?}\label{sec:Creating New Device Types / What Device Number?}
 
-- 
cgit v1.2.3

