Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Parav Pandit <parav@nvidia.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	virtio-comment <virtio-comment@lists.linux.dev>,
	Cornelia Huck <cohuck@redhat.com>
Cc: Max Gurtovoy <mgurtovoy@nvidia.com>,
	Linlin Zhang <linlin.zhang@oss.qualcomm.com>,
	<neeraj.soni@oss.qualcomm.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	Parav Pandit <parav@nvidia.com>
Subject: [PATCH 1/6] transport-mmio: Introduce administration virtqueues
Date: Sat, 17 Oct 2026 14:45:51 +0300	[thread overview]
Message-ID: <20261017114556.1701355-2-parav@nvidia.com> (raw)
In-Reply-To: <20261017114556.1701355-1-parav@nvidia.com>

Administration virtqueues and group administration commands are
defined in a transport independent way, but so far only the PCI
transport describes how a device exposes administration virtqueues.

As the first step towards supporting them over MMIO, describe how
administration virtqueues fit into the MMIO transport: they are
regular virtqueues identified by an index, which are configured,
enabled, reset and notified like any other virtqueue, and which occupy
a contiguous range of indices beyond all other virtqueues.

Only the Self group type is applicable to the MMIO transport; state
this explicitly.

Subsequent patches add the registers to discover the administration
virtqueues and the related requirements.

Signed-off-by: Parav Pandit <parav@nvidia.com>
---
 transport-mmio.tex | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/transport-mmio.tex b/transport-mmio.tex
index cddbcc9..e015bd7 100644
--- a/transport-mmio.tex
+++ b/transport-mmio.tex
@@ -446,6 +446,27 @@ \subsubsection{Notifications From The Device}\label{sec:Virtio Transport Options
 it by writing a bit mask corresponding to the handled events to the
 InterruptACK register.
 
+\subsubsection{Administration Virtqueues}\label{sec:Virtio Transport Options / Virtio Over MMIO / MMIO-specific Initialization And Device Operation / Administration Virtqueues}
+
+A memory mapped virtio device can expose one or more administration
+virtqueues (see
+\ref{sec:Basic Facilities of a Virtio Device / Administration Virtqueues}~\nameref{sec:Basic Facilities of a Virtio Device / Administration Virtqueues}),
+which the driver uses to submit group administration commands (see
+\ref{sec:Basic Facilities of a Virtio Device / Device groups / Group administration commands}~\nameref{sec:Basic Facilities of a Virtio Device / Device groups / Group administration commands}).
+
+Only group administration commands of the Self group type are
+applicable to a memory mapped virtio device.
+
+An administration virtqueue is a virtqueue like any other: it is
+identified by its virtqueue index and
+the driver configures, enables, resets and notifies it using the same
+registers and procedures as for any other virtqueue of the device, see
+\ref{sec:Virtio Transport Options / Virtio Over MMIO / MMIO-specific Initialization And Device Operation / Virtqueue Configuration}~\nameref{sec:Virtio Transport Options / Virtio Over MMIO / MMIO-specific Initialization And Device Operation / Virtqueue Configuration}.
+
+The device reports a contiguous range of administration virtqueues.
+This range is located beyond the indices of all other virtqueues of
+the device.
+
 \subsection{Legacy interface}\label{sec:Virtio Transport Options / Virtio Over MMIO / Legacy interface}
 
 The legacy MMIO transport used page-based addressing, resulting
-- 
2.43.0


  reply	other threads:[~2026-10-17 11:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17 11:45 [PATCH 0/6] transport-mmio: Support administration virtqueues Parav Pandit
2026-10-17 11:45 ` Parav Pandit [this message]
2026-10-17 11:45 ` [PATCH 2/6] transport-mmio: Add administration virtqueue registers Parav Pandit
2026-10-17 11:45 ` [PATCH 3/6] transport-mmio: Remove ADMIN_VQ from features reserved for future use Parav Pandit
2026-10-17 11:45 ` [PATCH 4/6] admin: Reference transport specific administration virtqueue discovery Parav Pandit
2026-10-17 11:45 ` [PATCH 5/6] transport-pci: Add missing driver requirement for admin queue fields Parav Pandit
2026-10-17 11:45 ` [PATCH 6/6] transport-mmio: Add administration virtqueue requirements Parav Pandit
2026-10-17 13:22 ` [PATCH 0/6] transport-mmio: Support administration virtqueues Michael S. Tsirkin

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=20261017114556.1701355-2-parav@nvidia.com \
    --to=parav@nvidia.com \
    --cc=cohuck@redhat.com \
    --cc=linlin.zhang@oss.qualcomm.com \
    --cc=mgurtovoy@nvidia.com \
    --cc=mst@redhat.com \
    --cc=neeraj.soni@oss.qualcomm.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-comment@lists.linux.dev \
    /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