As we are going to add more virtqueues, when talking
about the requestq be specific and mention it by name
as opposed to just generally "the virtqueue".
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>
---
virtio-rng.tex | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/virtio-rng.tex b/virtio-rng.tex
index c26f589..1ec7164 100644
--- a/virtio-rng.tex
+++ b/virtio-rng.tex
@@ -20,23 +20,24 @@ \subsection{Device configuration layout}\label{sec:Device
Types / Entropy Device
\subsection{Device Initialization}\label{sec:Device Types / Entropy Device /
Device Initialization}
\begin{enumerate}
-\item The virtqueue is initialized
+\item The \field{requestq} virtqueue is initialized
\end{enumerate}
\subsection{Device Operation}\label{sec:Device Types / Entropy Device / Device
Operation}
When the driver requires random bytes, it places the descriptor
-of one or more buffers in the queue. It will be completely filled
+of one or more buffers in the \field{requestq} virtqueue. It will be
completely filled
by random data by the device.
\drivernormative{\subsubsection}{Device Operation}{Device Types / Entropy
Device / Device Operation}
-The driver MUST NOT place device-readable buffers into the queue.
+The driver MUST NOT place device-readable buffers into the \field{requestq}
virtqueue.
The driver MUST examine the length written by the device to determine
how many random bytes were received.
\devicenormative{\subsubsection}{Device Operation}{Device Types / Entropy
Device / Device Operation}
-The device MUST place one or more random bytes into the buffer, but it
+The device MUST place one or more random bytes into the buffer
+made available to it through \field{requestq}, but it
MAY use less than the entire buffer length.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
