summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorrusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2013-10-31 22:48:46 +0000
committerrusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>2013-10-31 22:48:46 +0000
commitba0bc5268bd656f7d7e6059946ea1ea3c7a32a3e (patch)
treea1e82aba0284202bedef88154e54b31c7a76f4ab
parenta009ddd167d1e0d08979df8f7d4ed0736a4290f7 (diff)
virtqueue endian-ness
make all ring structures LE resolves VIRTIO-9 Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Rusty Russell <rusty@au1.ibm.com> git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@76 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
-rw-r--r--virtio-v1.0-wd01-part1-specification.txt8
1 files changed, 3 insertions, 5 deletions
diff --git a/virtio-v1.0-wd01-part1-specification.txt b/virtio-v1.0-wd01-part1-specification.txt
index 6b5d46e..849acd4 100644
--- a/virtio-v1.0-wd01-part1-specification.txt
+++ b/virtio-v1.0-wd01-part1-specification.txt
@@ -340,14 +340,12 @@ The legacy virtqueue layout structure therefore looks like this:
struct vring_used used;
};
-2.1.4.1. A Note on Virtqueue Endianness
+2.1.4.1. Legacy Interfaces: A Note on Virtqueue Endianness
--------------------------------------
Note that the endian of fields and in the virtqueue is the native
-endian of the guest, not little-endian as PCI normally is. This makes
-for simpler guest code, and it is assumed that the host already has to
-be deeply aware of the guest endian so such an “endian-aware” device
-is not a significant issue.
+endian of the guest, not little-endian as PCI normally is.
+It is assumed that the host is already aware of the guest endian.
2.1.4.2. Message Framing
-----------------------