From: David Edmondson <david.edmondson@oracle.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
virtio-dev@lists.oasis-open.org, jasowang@redhat.com,
cohuck@redhat.com, sgarzare@redhat.com, stefanha@redhat.com,
nrupal.jani@intel.com, Piotr.Uminski@intel.com,
hang.yuan@intel.com, virtio@lists.oasis-open.org,
Zhu Lingshan <lingshan.zhu@intel.com>,
pasic@linux.ibm.com, Shahaf Shuler <shahafs@nvidia.com>,
Parav Pandit <parav@nvidia.com>,
virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH v10 05/10] pci: add admin vq registers to virtio over pci
Date: Wed, 15 Feb 2023 08:49:00 +0000 [thread overview]
Message-ID: <m2mt5fxq32.fsf@oracle.com> (raw)
In-Reply-To: <a40f3ad9-2a63-84c1-39d3-ddf36355d3b5@nvidia.com>
On Wednesday, 2023-02-15 at 02:53:34 +02, Max Gurtovoy wrote:
> On 13/02/2023 14:21, David Edmondson wrote:
>> On Thursday, 2023-02-09 at 07:13:48 -05, Michael S. Tsirkin wrote:
>>> @@ -1031,6 +1035,19 @@ \subsubsection{Common configuration structure layout}\label{sec:Virtio Transport
>>> This field exists only if VIRTIO_F_RING_RESET has been
>>> negotiated. (see \ref{sec:Basic Facilities of a Virtio Device / Virtqueues / Virtqueue Reset}).
>>> +\item[\field{admin_queue_index}]
>>> + The device uses this to report the index of the first administration virtqueue.
>>> + This field is valid only if VIRTIO_F_ADMIN_VQ has been negotiated.
>>> +\item[\field{admin_queue_num}]
>>> + The device uses this to report the number of the
>>> + supported administration virtqueues. Virtqueues with index
>>> + between \field{admin_queue_index} and (\field{admin_queue_index} +
>>> + \field{admin_queue_num}) inclusive serve as administration
>>> + virtqueues.
>>> + Thus the number of administration virtqueues equals
>>> + (\field{admin_queue_num} + 1).
>> Really the number of queues is "admin_queue_num + 1"?
>> That seems ... odd.
>
> It's not odd if we'll mention that this is a zero based value.
> MST, can you add it please for the next version ?
The field is called ...num, which makes it seem like a count of things,
when in reality it's the highest index. Perhaps the name could more
accurately reflect the intent?
>
>>
>>> + This field is valid only if VIRTIO_F_ADMIN_VQ has been
>>> + negotiated.
>>> \end{description}
>>> \devicenormative{\paragraph}{Common configuration structure
>>> layout}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device
>>> Layout / Common configuration structure layout}
>>> @@ -1117,6 +1134,14 @@ \subsubsection{Common configuration structure layout}\label{sec:Virtio Transport
>>> were used before the queue reset.
>>> (see \ref{sec:Basic Facilities of a Virtio Device / Virtqueues / Virtqueue Reset}).
>>> +If VIRTIO_F_ADMIN_VQ has been negotiated, and if the driver
>>> +configures any administration virtqueues, the driver MUST
>>> +configure the administration virtqueues using the index
>>> +in the range \field{admin_queue_index} to
>>> +\field{admin_queue_index} + \field{admin_queue_num} inclusive.
>>> +The driver MAY configure less administration virtqueues than
>>> +supported by the device.
>>> +
>>> \subsubsection{Notification structure layout}\label{sec:Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Notification capability}
>>> The notification location is found using the
>>> VIRTIO_PCI_CAP_NOTIFY_CFG
>>> @@ -7684,6 +7709,15 @@ \chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits}
>>> \item[VIRTIO_F_ADMIN_VQ(41)] This feature indicates that the
>>> device exposes one or more
>>> administration virtqueues.
>>> + At the moment this feature is only supported for devices using
>>> + \ref{sec:Virtio Transport Options / Virtio Over PCI
>>> + Bus}~\nameref{sec:Virtio Transport Options / Virtio Over PCI Bus}
>>> + as the transport and is reserved for future use for
>>> + devices using other transports (see
>>> + \ref{drivernormative:Basic Facilities of a Virtio Device / Feature Bits}
>>> + and
>>> + \ref{devicenormative:Basic Facilities of a Virtio Device / Feature Bits} for
>>> + handling features reserved for future use.
>>> \end{description}
--
Stop the music and go home.
next prev parent reply other threads:[~2023-02-15 8:49 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 12:13 [virtio-dev] [PATCH v10 00/10] Introduce device group and device management Michael S. Tsirkin
2023-02-09 12:13 ` [PATCH v10 01/10] virtio: document forward compatibility guarantees Michael S. Tsirkin
2023-02-09 14:52 ` [virtio-comment] Re: [virtio-dev] " David Edmondson
2023-02-13 12:06 ` [virtio-dev] " Cornelia Huck
2023-02-13 12:28 ` Michael S. Tsirkin
2023-02-11 18:50 ` [virtio-dev] " Parav Pandit
2023-02-09 12:13 ` [PATCH v10 02/10] admin: introduce device group and related concepts Michael S. Tsirkin
2023-02-09 15:00 ` [virtio-comment] " David Edmondson
2023-02-09 15:13 ` Michael S. Tsirkin
2023-02-09 15:22 ` David Edmondson
2023-02-09 17:47 ` Max Gurtovoy
2023-02-09 19:58 ` Michael S. Tsirkin
2023-02-12 12:10 ` Max Gurtovoy
2023-02-12 13:15 ` Michael S. Tsirkin
2023-02-12 14:34 ` Max Gurtovoy
2023-02-12 20:19 ` Michael S. Tsirkin
2023-02-12 22:49 ` Max Gurtovoy
2023-02-13 8:12 ` Michael S. Tsirkin
2023-02-13 9:20 ` [virtio-dev] " Zhu, Lingshan
2023-02-13 10:55 ` [virtio] " Michael S. Tsirkin
2023-02-13 10:28 ` Max Gurtovoy
2023-02-14 1:22 ` Parav Pandit
2023-02-11 16:52 ` Parav Pandit
2023-02-11 18:50 ` Parav Pandit
2023-02-13 12:20 ` [virtio] " Cornelia Huck
2023-02-13 12:28 ` Michael S. Tsirkin
2023-02-09 12:13 ` [PATCH v10 03/10] admin: introduce group administration commands Michael S. Tsirkin
2023-02-10 8:24 ` [virtio-comment] " Zhu Lingshan
2023-02-11 18:50 ` Parav Pandit
2023-02-12 9:49 ` Michael S. Tsirkin
2023-02-13 0:54 ` Max Gurtovoy
2023-02-13 8:16 ` Michael S. Tsirkin
2023-02-13 10:35 ` [virtio-comment] " Max Gurtovoy
2023-02-13 12:42 ` Cornelia Huck
2023-02-13 13:11 ` Max Gurtovoy
2023-02-13 13:13 ` [virtio] " Cornelia Huck
2023-02-13 13:26 ` Max Gurtovoy
2023-02-13 13:36 ` [virtio] " Cornelia Huck
2023-02-13 15:07 ` Max Gurtovoy
2023-02-13 20:29 ` [virtio] " Michael S. Tsirkin
2023-02-14 9:01 ` [virtio-comment] " Cornelia Huck
2023-02-14 1:18 ` Parav Pandit
2023-02-14 7:46 ` Michael S. Tsirkin
2023-02-14 16:44 ` Parav Pandit
2023-02-14 21:57 ` Michael S. Tsirkin
2023-02-15 4:46 ` [virtio-comment] " Parav Pandit
2023-02-15 5:13 ` Michael S. Tsirkin
2023-02-13 12:37 ` [virtio-comment] Re: [virtio-dev] " David Edmondson
2023-02-15 5:17 ` Parav Pandit
2023-02-15 5:18 ` Michael S. Tsirkin
2023-02-09 12:13 ` [PATCH v10 04/10] admin: introduce virtio admin virtqueues Michael S. Tsirkin
2023-02-11 18:50 ` Parav Pandit
2023-02-09 12:13 ` [PATCH v10 05/10] pci: add admin vq registers to virtio over pci Michael S. Tsirkin
2023-02-11 18:52 ` Parav Pandit
2023-02-13 12:21 ` [virtio-comment] " David Edmondson
2023-02-15 0:53 ` Max Gurtovoy
2023-02-15 5:09 ` Michael S. Tsirkin
2023-02-15 8:49 ` David Edmondson [this message]
2023-02-09 12:13 ` [PATCH v10 06/10] mmio: document ADMIN_VQ as reserved Michael S. Tsirkin
2023-02-11 18:52 ` Parav Pandit
2023-02-15 0:56 ` Max Gurtovoy
2023-02-09 12:13 ` [PATCH v10 07/10] ccw: " Michael S. Tsirkin
2023-02-13 12:49 ` [virtio-comment] " Cornelia Huck
2023-02-15 0:58 ` Max Gurtovoy
2023-02-09 12:14 ` [PATCH v10 08/10] admin: command list discovery Michael S. Tsirkin
2023-02-09 17:04 ` Uminski, Piotr
2023-02-11 18:52 ` Parav Pandit
2023-02-13 5:41 ` [virtio-dev] " Zhu Lingshan
2023-02-13 12:27 ` [virtio-comment] " David Edmondson
2023-02-09 12:14 ` [PATCH v10 09/10] admin: conformance clauses Michael S. Tsirkin
2023-02-11 16:43 ` Parav Pandit
2023-02-13 6:43 ` [virtio-comment] Re: [virtio-dev] " Zhu Lingshan
2023-02-13 10:51 ` Michael S. Tsirkin
2023-02-13 13:42 ` [virtio-comment] " David Edmondson
2023-02-09 12:14 ` [PATCH v10 10/10] ccw: document more reserved features Michael S. Tsirkin
2023-02-13 12:54 ` [virtio] " Cornelia Huck
2023-02-13 13:04 ` Cornelia Huck
2023-02-11 18:49 ` [PATCH v10 00/10] Introduce device group and device management Parav Pandit
2023-02-12 9:42 ` Michael S. Tsirkin
2023-02-14 0:52 ` [virtio-comment] " 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=m2mt5fxq32.fsf@oracle.com \
--to=david.edmondson@oracle.com \
--cc=Piotr.Uminski@intel.com \
--cc=cohuck@redhat.com \
--cc=hang.yuan@intel.com \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=mgurtovoy@nvidia.com \
--cc=mst@redhat.com \
--cc=nrupal.jani@intel.com \
--cc=parav@nvidia.com \
--cc=pasic@linux.ibm.com \
--cc=sgarzare@redhat.com \
--cc=shahafs@nvidia.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtio@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