All of lore.kernel.org
 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 3/6] transport-mmio: Remove ADMIN_VQ from features reserved for future use
Date: Sat, 17 Oct 2026 14:45:53 +0300	[thread overview]
Message-ID: <20261017114556.1701355-4-parav@nvidia.com> (raw)
In-Reply-To: <20261017114556.1701355-1-parav@nvidia.com>

Commit a9a59f70be46 ("mmio: document ADMIN_VQ as reserved") listed
VIRTIO_F_ADMIN_VQ as reserved for devices and drivers using the MMIO
transport, because MMIO had no registers to expose administration
virtqueues.

Now that the MMIO transport defines AdminQueueIndex and AdminQueueNum,
VIRTIO_F_ADMIN_VQ is no longer reserved for MMIO. Remove it from the
MMIO list of features reserved for future use; as it was the only
entry, remove the whole section.

Also update the VIRTIO_F_ADMIN_VQ description to state that the feature
is supported for both the PCI and the MMIO transports, and remains
reserved for other transports.

Signed-off-by: Parav Pandit <parav@nvidia.com>
---
 content.tex        |  3 +++
 transport-mmio.tex | 12 ------------
 2 files changed, 3 insertions(+), 12 deletions(-)

diff --git a/content.tex b/content.tex
index 243ce2d..3af0b30 100644
--- a/content.tex
+++ b/content.tex
@@ -935,6 +935,9 @@ \chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits}
   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}
+	  or
+  \ref{sec:Virtio Transport Options / Virtio Over
+	  MMIO}~\nameref{sec:Virtio Transport Options / Virtio Over MMIO}
 	  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}
diff --git a/transport-mmio.tex b/transport-mmio.tex
index 3c5aa6b..c537e85 100644
--- a/transport-mmio.tex
+++ b/transport-mmio.tex
@@ -664,15 +664,3 @@ \subsection{Legacy interface}\label{sec:Virtio Transport Options / Virtio Over M
 \end{enumerate}
 
 Notification mechanisms did not change.
-
-\subsection{Features reserved for future use}\label{sec:Virtio Transport Options / Virtio Over MMIO / Features reserved for future use}
-
-Devices and drivers utilizing Virtio Over MMIO
-do not support the following features:
-\begin{itemize}
-
-\item VIRTIO_F_ADMIN_VQ
-
-\end{itemize}
-
-These features are reserved for future use.
-- 
2.43.0


  parent 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 ` [PATCH 1/6] transport-mmio: Introduce " Parav Pandit
2026-10-17 11:45 ` [PATCH 2/6] transport-mmio: Add administration virtqueue registers Parav Pandit
2026-10-17 11:45 ` Parav Pandit [this message]
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-4-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 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.