From ba0bc5268bd656f7d7e6059946ea1ea3c7a32a3e Mon Sep 17 00:00:00 2001 From: rusty Date: Thu, 31 Oct 2013 22:48:46 +0000 Subject: virtqueue endian-ness make all ring structures LE resolves VIRTIO-9 Signed-off-by: Michael S. Tsirkin Signed-off-by: Rusty Russell git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@76 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652 --- virtio-v1.0-wd01-part1-specification.txt | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) (limited to 'virtio-v1.0-wd01-part1-specification.txt') 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 ----------------------- -- cgit v1.2.3