diff options
author | mstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2015-03-25 17:06:22 +0000 |
---|---|---|
committer | mstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2015-03-25 17:06:22 +0000 |
commit | d5d4b0c8bb2edb6f7aa771a7a060bf7c9a5f864a (patch) | |
tree | 9f1a127dc40e5cea3718f3bdc14745d3430ea854 | |
parent | c407b04f9ddd80af2787b3b7f4fa3430c4100d22 (diff) |
document idx field in virtqueue used ring
Section 2.4.8 The Virtqueue Used Ring
lists the idx field, but never documents it.
VIRTIO-136.
Reported-by: Jason Wang <jasowang@redhat.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@486 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
-rw-r--r-- | content.tex | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/content.tex b/content.tex index d34685d..c9440a4 100644 --- a/content.tex +++ b/content.tex @@ -595,6 +595,9 @@ for drivers using untrusted buffers: if you do not know exactly how much has been written by the device, you usually have to zero the buffer to ensure no data leakage occurs. +\field{idx} field indicates where the driver would put the next descriptor +entry in the ring (modulo the queue size). This starts at 0, and increases. + \begin{note} The legacy \hyperref[intro:Virtio PCI Draft]{[Virtio PCI Draft]} referred to these structures as vring_used and vring_used_elem, and |