From: Parav Pandit <parav@nvidia.com>
To: mst@redhat.com, virtio-dev@lists.oasis-open.org, cohuck@redhat.com
Cc: virtio-comment@lists.oasis-open.org, shahafs@nvidia.com,
Parav Pandit <parav@nvidia.com>
Subject: [PATCH] content.tex Fix Driver notifications label
Date: Fri, 3 Feb 2023 20:35:32 +0200 [thread overview]
Message-ID: <20230203183532.90685-1-parav@nvidia.com> (raw)
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 <parav@nvidia.com>
---
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
next reply other threads:[~2023-02-03 18:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 18:35 Parav Pandit [this message]
2023-02-10 11:23 ` [virtio-dev] Re: [PATCH] content.tex Fix Driver notifications label Cornelia Huck
2023-02-15 5:31 ` Parav Pandit
2023-02-15 11:14 ` Michael S. Tsirkin
2023-02-15 12:19 ` [virtio-comment] " Cornelia Huck
2023-02-15 12:59 ` Michael S. Tsirkin
2023-02-15 15:08 ` [virtio-comment] " Cornelia Huck
2023-02-15 21:53 ` Parav Pandit
2023-02-16 0:20 ` Michael S. Tsirkin
2023-02-16 5:36 ` Parav Pandit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230203183532.90685-1-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox