diff options
| author | rusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2014-02-12 03:15:07 +0000 |
|---|---|---|
| committer | rusty <rusty@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2014-02-12 03:15:07 +0000 |
| commit | eb1dc6c33ea33f450d8e2fbf115dc486a52dc840 (patch) | |
| tree | b1642bec0691704b47c5d7c67c4a7c1c16b40f67 /content.tex | |
| parent | b08cb60c023467772636934451352663254e1ba0 (diff) | |
Feedback #4: applied.
As per minutes:
https://lists.oasis-open.org/archives/virtio/201402/msg00121.html
Signed-off-by: Rusty Russell <rusty@au1.ibm.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@235 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
Diffstat (limited to 'content.tex')
| -rw-r--r-- | content.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/content.tex b/content.tex index 67219a7..d5a775a 100644 --- a/content.tex +++ b/content.tex @@ -424,7 +424,7 @@ written by the driver and read by the device. The “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. -If the VIRTIO_RING_F_INDIRECT_DESC feature bit is not negotiated, the +If the VIRTIO_RING_F_EVENT_IDX feature bit is not negotiated, the “flags” field offers a crude interrupt control mechanism. The driver MUST set this to 0 or 1: 1 indicates that the device SHOULD NOT send an interrupt when it consumes a descriptor chain from the available @@ -474,7 +474,7 @@ 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. -If the VIRTIO_RING_F_INDIRECT_DESC feature bit is not negotiated, the +If the VIRTIO_RING_F_EVENT_IDX feature bit is not negotiated, the “flags” field offers a crude interrupt control mechanism. The driver MUST initialize this to 0, the device MUST set this to 0 or 1: 1 indicates that the driver SHOULD NOT send an notification when it adds |