diff options
| author | mstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2015-04-29 11:08:43 +0000 |
|---|---|---|
| committer | mstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2015-04-29 11:08:43 +0000 |
| commit | 12e4378536ea473f578edf05b83c78b9f846d516 (patch) | |
| tree | b0a9ac7f9e513bc26b39ff0b0c44305daba841f1 | |
| parent | 4ce541760523e7e1dba274d4e0c98473d93f61c0 (diff) | |
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
| -rw-r--r-- | newdevice.tex | 5 |
1 files changed, 3 insertions, 2 deletions
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?} |