Driver notifications section is under "Basic Facilities of a Virtio Device". However, the label is placed under "Virtqueues" section.
Fix the label references. Signed-off-by: Parav Pandit <[email protected]> --- content.tex | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/content.tex b/content.tex index df5ce16..874714f 100644 --- a/content.tex +++ b/content.tex @@ -396,7 +396,7 @@ \subsubsection{Virtqueue Re-enable}\label{sec:Basic Facilities of a Virtio Devic \input{packed-ring.tex} -\section{Driver Notifications} \label{sec:Virtqueues / Driver notifications} +\section{Driver Notifications} \label{sec:Basic Facilities of a Virtio Device / Driver notifications} The driver is sometimes required to send an available buffer notification to the device. @@ -1624,7 +1624,7 @@ \subsubsection{Available Buffer Notifications}\label{sec:Virtio Transport Option the following 32-bit value to the Queue Notify address: \lstinputlisting{notifications-le.c} -See \ref{sec:Virtqueues / Driver notifications}~\nameref{sec:Virtqueues / Driver notifications} +See \ref{sec:Basic Facilities of a Virtio Device / Driver notifications}~\nameref{sec:Basic Facilities of a Virtio Device / Driver notifications} for the definition of the components. See \ref{sec:Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Notification capability} @@ -1879,7 +1879,7 @@ \subsection{MMIO Device Register Layout}\label{sec:Virtio Transport Options / Vi \lstinputlisting{notifications-le.c} - See \ref{sec:Virtqueues / Driver notifications}~\nameref{sec:Virtqueues / Driver notifications} + See \ref{sec:Basic Facilities of a Virtio Device / Driver notifications}~\nameref{sec:Basic Facilities of a Virtio Device / Driver notifications} for the definition of the components. } \hline @@ -2123,7 +2123,7 @@ \subsubsection{Available Buffer Notifications}\label{sec:Virtio Transport Option the following 32-bit value to \field{QueueNotify}: \lstinputlisting{notifications-le.c} -See \ref{sec:Virtqueues / Driver notifications}~\nameref{sec:Virtqueues / Driver notifications} +See \ref{sec:Basic Facilities of a Virtio Device / Driver notifications}~\nameref{sec:Basic Facilities of a Virtio Device / Driver notifications} for the definition of the components. \subsubsection{Notifications From The Device}\label{sec:Virtio Transport Options / Virtio Over MMIO / MMIO-specific Initialization And Device Operation / Notifications From The Device} @@ -2845,7 +2845,7 @@ \subsubsection{Guest->Host Notification}\label{sec:Virtio Transport Options / Vi the value has the following format: \lstinputlisting{notifications-be.c} -See \ref{sec:Virtqueues / Driver notifications}~\nameref{sec:Virtqueues / Driver notifications} +See \ref{sec:Basic Facilities of a Virtio Device / Driver notifications}~\nameref{sec:Basic Facilities of a Virtio Device / Driver notifications} for the definition of the components. \devicenormative{\paragraph}{Guest->Host Notification}{Virtio Transport Options / Virtio over channel I/O / Device Operation / Guest->Host Notification} @@ -3091,12 +3091,12 @@ \chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits} \item[VIRTIO_F_NOTIFICATION_DATA(38)] This feature indicates that the driver passes extra data (besides identifying the virtqueue) in its device notifications. - See \ref{sec:Virtqueues / Driver notifications}~\nameref{sec:Virtqueues / Driver notifications}. + See \ref{sec:Basic Facilities of a Virtio Device / Driver notifications}~\nameref{sec:Basic Facilities of a Virtio Device / Driver notifications}. \item[VIRTIO_F_NOTIF_CONFIG_DATA(39)] This feature indicates that the driver uses the data provided by the device as a virtqueue identifier in available buffer notifications. - As mentioned in section \ref{sec:Virtqueues / Driver notifications}, when the + As mentioned in section \ref{sec:Basic Facilities of a Virtio Device / Driver notifications}, when the driver is required to send an available buffer notification to the device, it sends the virtqueue number to be notified. The method of delivering notifications is transport specific. -- 2.26.2 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
