public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio-comment@lists.oasis-open.org,
	virtio-dev@lists.oasis-open.org, jasowang@redhat.com,
	cohuck@redhat.com, sgarzare@redhat.com, nrupal.jani@intel.com,
	Piotr.Uminski@intel.com, hang.yuan@intel.com,
	virtio@lists.oasis-open.org, Jiri Pirko <jiri@nvidia.com>,
	Zhu Lingshan <lingshan.zhu@intel.com>,
	pasic@linux.ibm.com, Shahaf Shuler <shahafs@nvidia.com>,
	Parav Pandit <parav@nvidia.com>,
	Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [virtio-dev] Re: [PATCH v11 05/10] pci: add admin vq registers to virtio over pci
Date: Tue, 4 Apr 2023 08:52:28 -0400	[thread overview]
Message-ID: <20230404125228.GD428487@fedora> (raw)
In-Reply-To: <fbf6f659974884f7430ec7ef68028305d7acee0c.1680533760.git.mst@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]

On Mon, Apr 03, 2023 at 11:03:29AM -0400, Michael S. Tsirkin wrote:
> @@ -1033,6 +1037,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} - 1) inclusive serve as administration
> +	virtqueues.
> +	The value 0 indicates no supported administration virtqueues.
> +	This field is valid only if VIRTIO_F_ADMIN_VQ has been
> +	negotiated.
>  \end{description}

Maybe add a device-normative statement that [admin_queue_index,
admin_queue_index + admin_queue_num) must be located after
device-specific virtqueues?

That would remind implementers that the device-specific virtqueue layout
needs to be followed and cannot be modified by the presence of
Administration Virtqueues.

>  \devicenormative{\paragraph}{Common configuration structure layout}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Common configuration structure layout}
> @@ -1119,6 +1136,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} - 1 inclusive.
> +The driver MAY configure less administration virtqueues than

s/less/fewer/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-04-04 12:52 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 15:02 [virtio-dev] [PATCH v11 00/10] Introduce device group and device management Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 01/10] virtio: document forward compatibility guarantees Michael S. Tsirkin
2023-04-06  7:15   ` [virtio-dev] " Zhu, Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 02/10] admin: introduce device group and related concepts Michael S. Tsirkin
2023-04-04 11:38   ` [virtio-dev] " Stefan Hajnoczi
2023-04-06  3:42   ` Parav Pandit
2023-04-10 13:23     ` Michael S. Tsirkin
2023-04-10 16:42       ` [virtio-dev] " Parav Pandit
2023-04-24 16:30         ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-24 16:45           ` [virtio-dev] RE: [virtio] " Parav Pandit
2023-04-24 20:32             ` [virtio-dev] " Michael S. Tsirkin
2023-04-06  7:16   ` [virtio-dev] " Zhu, Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 03/10] admin: introduce group administration commands Michael S. Tsirkin
2023-04-04 11:50   ` [virtio-dev] " Stefan Hajnoczi
2023-04-06  3:58   ` Parav Pandit
2023-04-06  7:16   ` Zhu, Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 04/10] admin: introduce virtio admin virtqueues Michael S. Tsirkin
2023-04-04 11:58   ` [virtio-dev] " Stefan Hajnoczi
2023-04-06  4:08   ` Parav Pandit
2023-04-10 13:22     ` Michael S. Tsirkin
2023-04-10 14:22       ` [virtio-dev] " Parav Pandit
2023-04-10 20:04         ` [virtio-dev] " Michael S. Tsirkin
2023-04-11 13:39           ` [virtio-dev] " Parav Pandit
2023-04-11 14:01             ` [virtio-dev] " Michael S. Tsirkin
2023-04-11 15:46               ` [virtio-dev] " Parav Pandit
2023-04-06  7:17   ` [virtio-dev] " Zhu Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 05/10] pci: add admin vq registers to virtio over pci Michael S. Tsirkin
2023-04-04 12:52   ` Stefan Hajnoczi [this message]
2023-04-06  4:14   ` [virtio-dev] " Parav Pandit
2023-04-24 15:36     ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-06  7:17   ` [virtio-dev] Re: [virtio] " Zhu, Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 06/10] mmio: document ADMIN_VQ as reserved Michael S. Tsirkin
2023-04-03 15:54   ` [virtio-dev] " Parav Pandit
2023-04-24 15:38     ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-06  7:18   ` [virtio-dev] Re: [virtio-comment] " Zhu Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 07/10] ccw: " Michael S. Tsirkin
2023-04-03 15:55   ` [virtio-dev] " Parav Pandit
2023-04-03 17:29     ` Michael S. Tsirkin
2023-04-06  4:15   ` Parav Pandit
2023-04-06  7:18   ` [virtio-dev] " Zhu Lingshan
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 08/10] admin: command list discovery Michael S. Tsirkin
2023-04-04 12:57   ` [virtio-dev] " Stefan Hajnoczi
2023-04-06  4:27   ` Parav Pandit
2023-04-24 16:13     ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-06  7:20   ` [virtio-dev] " Zhu Lingshan
2023-04-06 14:05     ` Parav Pandit
2023-04-07  2:01       ` Zhu, Lingshan
2023-04-07  7:34       ` Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] [PATCH v11 09/10] admin: conformance clauses Michael S. Tsirkin
2023-04-04 13:03   ` [virtio-dev] " Stefan Hajnoczi
2023-04-06  7:30   ` [virtio-dev] Re: [virtio] " Zhu, Lingshan
2023-04-24 16:17     ` [virtio-dev] Re: [virtio-comment] " Michael S. Tsirkin
2023-04-03 15:04 ` [virtio-dev] [PATCH v11 10/10] ccw: document more reserved features Michael S. Tsirkin
2023-04-06  7:31   ` [virtio-dev] Re: [virtio-comment] " Zhu Lingshan
2023-04-03 15:59 ` [virtio-dev] Re: [PATCH v11 00/10] Introduce device group and device management Parav Pandit
2023-04-03 16:39 ` Cornelia Huck
2023-04-03 17:31   ` Michael S. Tsirkin
2023-04-04  8:10     ` Cornelia Huck

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=20230404125228.GD428487@fedora \
    --to=stefanha@redhat.com \
    --cc=Piotr.Uminski@intel.com \
    --cc=cohuck@redhat.com \
    --cc=hang.yuan@intel.com \
    --cc=jasowang@redhat.com \
    --cc=jiri@nvidia.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=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