From: David Edmondson <david.edmondson@oracle.com>
To: Parav Pandit <parav@nvidia.com>,
mst@redhat.com, virtio-dev@lists.oasis-open.org,
pasic@linux.ibm.com, cohuck@redhat.com
Cc: sgarzare@redhat.com, virtio-comment@lists.oasis-open.org,
shahafs@nvidia.com, Parav Pandit <parav@nvidia.com>,
Jiri Pirko <jiri@nvidia.com>
Subject: Re: [virtio-comment] [PATCH v8 4/8] transport-mmio: Refer to the vq by its number
Date: Tue, 28 Mar 2023 15:05:20 +0100 [thread overview]
Message-ID: <m21ql9c6ov.fsf@oracle.com> (raw)
In-Reply-To: <20230327235936.414196-5-parav@nvidia.com>
Parav Pandit <parav@nvidia.com> writes:
> Currently specification uses virtqueue index and
> number interchangeably to refer to the virtqueue.
>
> Instead refer to it by its number.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/163
> Reviewed-by: Jiri Pirko <jiri@nvidia.com>
> Signed-off-by: Parav Pandit <parav@nvidia.com>
>
> ---
> changelog:
> v6->v7:
> - remove text around first vq as it is already covered in the basic
> virtqueues facility section
> ---
> transport-mmio.tex | 21 ++++++++-------------
> 1 file changed, 8 insertions(+), 13 deletions(-)
>
> diff --git a/transport-mmio.tex b/transport-mmio.tex
> index 3047633..2aa6627 100644
> --- a/transport-mmio.tex
> +++ b/transport-mmio.tex
> @@ -108,13 +108,12 @@ \subsection{MMIO Device Register Layout}\label{sec:Virtio Transport Options / Vi
> bits accessible by writing to \field{DriverFeatures}.
> }
> \hline
> - \mmioreg{QueueSel}{Virtual queue index}{0x030}{W}{%
> + \mmioreg{QueueSel}{Virtual queue number}{0x030}{W}{%
> Writing to this register selects the virtual queue that the
> following operations on \field{QueueSizeMax},
> \field{QueueSize}, \field{QueueReady},
> \field{QueueDescLow}, \field{QueueDescHigh}, \field{QueueDriverlLow}, \field{QueueDriverHigh},
> - \field{QueueDeviceLow}, \field{QueueDeviceHigh} and \field{QueueReset} apply to. The index
> - number of the first queue is zero (0x0).
> + \field{QueueDeviceLow}, \field{QueueDeviceHigh} and \field{QueueReset} apply to.
> }
> \hline
> \mmioreg{QueueSizeMax}{Maximum virtual queue size}{0x034}{R}{%
> @@ -149,7 +148,7 @@ \subsection{MMIO Device Register Layout}\label{sec:Virtio Transport Options / Vi
> there are new buffers to process in a queue.
>
> When VIRTIO_F_NOTIFICATION_DATA has not been negotiated,
> - the value written is the queue index.
> + the value written is the queue number.
Should "queue number" become "virtqueue number" everywhere?
Perhaps the introduction should indicate that "queue number" is another
term for "virtqueue number".
>
> When VIRTIO_F_NOTIFICATION_DATA has been negotiated,
> the \field{Notification data} value has the following format:
> @@ -363,8 +362,7 @@ \subsubsection{Virtqueue Configuration}\label{sec:Virtio Transport Options / Vir
> The driver will typically initialize the virtual queue in the following way:
>
> \begin{enumerate}
> -\item Select the queue writing its index (first queue is 0) to
> - \field{QueueSel}.
> +\item Select the queue writing its number to \field{QueueSel}.
s/queue/queue by/
>
> \item Check if the queue is not already in use: read \field{QueueReady},
> and expect a returned value of zero (0x0).
> @@ -392,7 +390,7 @@ \subsubsection{Available Buffer Notifications}\label{sec:Virtio Transport Option
>
> When VIRTIO_F_NOTIFICATION_DATA has not been negotiated,
> the driver sends an available buffer notification to the device by writing
> -the 16-bit virtqueue index
> +the 16-bit virtqueue number
> of the queue to be notified to \field{QueueNotify}.
>
> When VIRTIO_F_NOTIFICATION_DATA has been negotiated,
> @@ -470,13 +468,11 @@ \subsection{Legacy interface}\label{sec:Virtio Transport Options / Virtio Over M
> (see QueuePFN).
> }
> \hline
> - \mmioreg{QueueSel}{Virtual queue index}{0x030}{W}{%
> + \mmioreg{QueueSel}{Virtual queue number}{0x030}{W}{%
> Writing to this register selects the virtual queue that the
> following operations on the \field{QueueSizeMax},
> \field{QueueSize}, \field{QueueAlign}
> - and \field{QueuePFN} registers apply to. The index
> - number of the first queue is zero (0x0).
> -.
> + and \field{QueuePFN} registers apply to.
> }
> \hline
> \mmioreg{QueueSizeMax}{Maximum virtual queue size}{0x034}{R}{%
> @@ -550,8 +546,7 @@ \subsection{Legacy interface}\label{sec:Virtio Transport Options / Virtio Over M
>
> The virtual queue is configured as follows:
> \begin{enumerate}
> -\item Select the queue writing its index (first queue is 0) to
> - \field{QueueSel}.
> +\item Select the queue writing its number to \field{QueueSel}.
s/queue/queue by/
>
> \item Check if the queue is not already in use: read \field{QueuePFN},
> expecting a returned value of zero (0x0).
> --
> 2.26.2
>
>
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/
--
I move with the movement and I have the touch.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
WARNING: multiple messages have this Message-ID (diff)
From: David Edmondson <david.edmondson@oracle.com>
To: Parav Pandit <parav@nvidia.com>,
mst@redhat.com, virtio-dev@lists.oasis-open.org,
pasic@linux.ibm.com, cohuck@redhat.com
Cc: sgarzare@redhat.com, virtio-comment@lists.oasis-open.org,
shahafs@nvidia.com, Parav Pandit <parav@nvidia.com>,
Jiri Pirko <jiri@nvidia.com>
Subject: [virtio-dev] Re: [virtio-comment] [PATCH v8 4/8] transport-mmio: Refer to the vq by its number
Date: Tue, 28 Mar 2023 15:05:20 +0100 [thread overview]
Message-ID: <m21ql9c6ov.fsf@oracle.com> (raw)
In-Reply-To: <20230327235936.414196-5-parav@nvidia.com>
Parav Pandit <parav@nvidia.com> writes:
> Currently specification uses virtqueue index and
> number interchangeably to refer to the virtqueue.
>
> Instead refer to it by its number.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/163
> Reviewed-by: Jiri Pirko <jiri@nvidia.com>
> Signed-off-by: Parav Pandit <parav@nvidia.com>
>
> ---
> changelog:
> v6->v7:
> - remove text around first vq as it is already covered in the basic
> virtqueues facility section
> ---
> transport-mmio.tex | 21 ++++++++-------------
> 1 file changed, 8 insertions(+), 13 deletions(-)
>
> diff --git a/transport-mmio.tex b/transport-mmio.tex
> index 3047633..2aa6627 100644
> --- a/transport-mmio.tex
> +++ b/transport-mmio.tex
> @@ -108,13 +108,12 @@ \subsection{MMIO Device Register Layout}\label{sec:Virtio Transport Options / Vi
> bits accessible by writing to \field{DriverFeatures}.
> }
> \hline
> - \mmioreg{QueueSel}{Virtual queue index}{0x030}{W}{%
> + \mmioreg{QueueSel}{Virtual queue number}{0x030}{W}{%
> Writing to this register selects the virtual queue that the
> following operations on \field{QueueSizeMax},
> \field{QueueSize}, \field{QueueReady},
> \field{QueueDescLow}, \field{QueueDescHigh}, \field{QueueDriverlLow}, \field{QueueDriverHigh},
> - \field{QueueDeviceLow}, \field{QueueDeviceHigh} and \field{QueueReset} apply to. The index
> - number of the first queue is zero (0x0).
> + \field{QueueDeviceLow}, \field{QueueDeviceHigh} and \field{QueueReset} apply to.
> }
> \hline
> \mmioreg{QueueSizeMax}{Maximum virtual queue size}{0x034}{R}{%
> @@ -149,7 +148,7 @@ \subsection{MMIO Device Register Layout}\label{sec:Virtio Transport Options / Vi
> there are new buffers to process in a queue.
>
> When VIRTIO_F_NOTIFICATION_DATA has not been negotiated,
> - the value written is the queue index.
> + the value written is the queue number.
Should "queue number" become "virtqueue number" everywhere?
Perhaps the introduction should indicate that "queue number" is another
term for "virtqueue number".
>
> When VIRTIO_F_NOTIFICATION_DATA has been negotiated,
> the \field{Notification data} value has the following format:
> @@ -363,8 +362,7 @@ \subsubsection{Virtqueue Configuration}\label{sec:Virtio Transport Options / Vir
> The driver will typically initialize the virtual queue in the following way:
>
> \begin{enumerate}
> -\item Select the queue writing its index (first queue is 0) to
> - \field{QueueSel}.
> +\item Select the queue writing its number to \field{QueueSel}.
s/queue/queue by/
>
> \item Check if the queue is not already in use: read \field{QueueReady},
> and expect a returned value of zero (0x0).
> @@ -392,7 +390,7 @@ \subsubsection{Available Buffer Notifications}\label{sec:Virtio Transport Option
>
> When VIRTIO_F_NOTIFICATION_DATA has not been negotiated,
> the driver sends an available buffer notification to the device by writing
> -the 16-bit virtqueue index
> +the 16-bit virtqueue number
> of the queue to be notified to \field{QueueNotify}.
>
> When VIRTIO_F_NOTIFICATION_DATA has been negotiated,
> @@ -470,13 +468,11 @@ \subsection{Legacy interface}\label{sec:Virtio Transport Options / Virtio Over M
> (see QueuePFN).
> }
> \hline
> - \mmioreg{QueueSel}{Virtual queue index}{0x030}{W}{%
> + \mmioreg{QueueSel}{Virtual queue number}{0x030}{W}{%
> Writing to this register selects the virtual queue that the
> following operations on the \field{QueueSizeMax},
> \field{QueueSize}, \field{QueueAlign}
> - and \field{QueuePFN} registers apply to. The index
> - number of the first queue is zero (0x0).
> -.
> + and \field{QueuePFN} registers apply to.
> }
> \hline
> \mmioreg{QueueSizeMax}{Maximum virtual queue size}{0x034}{R}{%
> @@ -550,8 +546,7 @@ \subsection{Legacy interface}\label{sec:Virtio Transport Options / Virtio Over M
>
> The virtual queue is configured as follows:
> \begin{enumerate}
> -\item Select the queue writing its index (first queue is 0) to
> - \field{QueueSel}.
> +\item Select the queue writing its number to \field{QueueSel}.
s/queue/queue by/
>
> \item Check if the queue is not already in use: read \field{QueuePFN},
> expecting a returned value of zero (0x0).
> --
> 2.26.2
>
>
> This publicly archived list offers a means to provide input to the
> OASIS Virtual I/O Device (VIRTIO) TC.
>
> In order to verify user consent to the Feedback License terms and
> to minimize spam in the list archive, subscription is required
> before posting.
>
> Subscribe: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> List archive: https://lists.oasis-open.org/archives/virtio-comment/
> Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
> List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
> Committee: https://www.oasis-open.org/committees/virtio/
> Join OASIS: https://www.oasis-open.org/join/
--
I move with the movement and I have the touch.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-03-28 14:05 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 23:59 [virtio-comment] [PATCH v8 0/8] Rename queue index to queue number Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 1/8] content: Add vq number text Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-28 13:56 ` [virtio-comment] " David Edmondson
2023-03-28 13:56 ` David Edmondson
2023-03-28 14:00 ` [virtio-comment] " Parav Pandit
2023-03-28 14:00 ` [virtio-dev] " Parav Pandit
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 2/8] transport-pci: Refer to the vq by its number Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-28 13:58 ` [virtio-comment] " David Edmondson
2023-03-28 13:58 ` David Edmondson
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 3/8] transport-mmio: Rename QueueNum register Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-28 14:01 ` [virtio-comment] " David Edmondson
2023-03-28 14:01 ` [virtio-dev] " David Edmondson
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 4/8] transport-mmio: Refer to the vq by its number Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-28 14:05 ` David Edmondson [this message]
2023-03-28 14:05 ` [virtio-dev] Re: [virtio-comment] " David Edmondson
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 5/8] transport-ccw: Rename queue depth/size to other transports Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-28 14:07 ` [virtio-comment] " David Edmondson
2023-03-28 14:07 ` [virtio-dev] " David Edmondson
2023-03-28 15:04 ` Parav Pandit
2023-03-28 15:04 ` [virtio-dev] " Parav Pandit
2023-03-28 16:16 ` David Edmondson
2023-03-28 16:16 ` [virtio-dev] " David Edmondson
2023-03-28 16:18 ` Parav Pandit
2023-03-28 16:18 ` [virtio-dev] " Parav Pandit
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 6/8] transport-ccw: Refer to the vq by its number Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 7/8] virtio-net: Avoid duplicate receive queue example Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-27 23:59 ` [virtio-comment] [PATCH v8 8/8] virtio-net: Describe RSS using rss rq id Parav Pandit
2023-03-27 23:59 ` [virtio-dev] " Parav Pandit
2023-03-28 14:13 ` [virtio-comment] " David Edmondson
2023-03-28 14:13 ` David Edmondson
2023-03-28 13:53 ` [virtio-comment] Re: [virtio-dev] [PATCH v8 0/8] Rename queue index to queue number David Edmondson
2023-03-28 13:53 ` David Edmondson
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=m21ql9c6ov.fsf@oracle.com \
--to=david.edmondson@oracle.com \
--cc=cohuck@redhat.com \
--cc=jiri@nvidia.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=pasic@linux.ibm.com \
--cc=sgarzare@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.