The drivernormative was simply in the wrong place. It does not belong
to the code example.
Signed-off-by: Halil Pasic <pa...@linux.vnet.ibm.com>
---
packed-ring.tex | 9 ++++-----
1 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/packed-ring.tex b/packed-ring.tex
index d93df3b..388850b 100644
--- a/packed-ring.tex
+++ b/packed-ring.tex
@@ -600,6 +600,10 @@ Suppression Structure Format}.
The driver has to be careful to expose the new \field{flags}
value before checking if notifications are suppressed.
+\drivernormative{\paragraph}{Notifying The Device}{Basic Facilities of a
Virtio Device / Packed Virtqueues / Supplying Buffers to The Device / Notifying
The Device}
+The driver MUST perform a suitable memory barrier before reading
+the Driver Event Suppression structure, to avoid missing a notification.
+
\subsubsection{Implementation Example}\label{sec:Basic Facilities of a Virtio
Device / Packed Virtqueues / Supplying Buffers to The Device / Implementation
Example}
Below is a driver code example. It does not attempt to reduce
@@ -658,11 +662,6 @@ if (vq->device_event.flags != RING_EVENT_FLAGS_DISABLE) {
\end{lstlisting}
-
-\drivernormative{\paragraph}{Notifying The Device}{Basic Facilities of a
Virtio Device / Packed Virtqueues / Supplying Buffers to The Device / Notifying
The Device}
-The driver MUST perform a suitable memory barrier before reading
-the Driver Event Suppression structure, to avoid missing a notification.
-
\subsection{Receiving Used Buffers From The Device}\label{sec:Basic Facilities
of a Virtio Device / Packed Virtqueues / Receiving Used Buffers From The Device}
Once the device has used buffers referred to by a descriptor (read from or
written to them, or
--
1.7.1
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
