From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, jasowang@redhat.com,
mst@redhat.com, cohuck@redhat.com, sgarzare@redhat.com,
stefanha@redhat.com, nrupal.jani@intel.com,
Piotr.Uminski@intel.com, hang.yuan@intel.com
Cc: virtio@lists.oasis-open.org,
Zhu Lingshan <lingshan.zhu@intel.com>,
oren@nvidia.com, parav@nvidia.com, shahafs@nvidia.com,
aadam@redhat.com, eperezma@redhat.com,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [PATCH RFC v7 5/8] MMIO: disallow using admin vq bit
Date: Fri, 12 Aug 2022 13:19:16 -0400 [thread overview]
Message-ID: <20220812171841.12183-6-mst@redhat.com> (raw)
In-Reply-To: <20220812171841.12183-1-mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
conformance.tex | 1 +
content.tex | 8 ++++++++
2 files changed, 9 insertions(+)
diff --git a/conformance.tex b/conformance.tex
index c3c1d3e..161b5e0 100644
--- a/conformance.tex
+++ b/conformance.tex
@@ -383,6 +383,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
An MMIO device MUST conform to the following normative statements:
\begin{itemize}
+\item \ref{devicenormative:Virtio Transport Options / Virtio Over MMIO / MMIO-specific Initialization And Device Operation / Device Initialization}
\item \ref{devicenormative:Virtio Transport Options / Virtio Over MMIO / MMIO Device Register Layout}
\end{itemize}
diff --git a/content.tex b/content.tex
index 297cb4a..76b5a28 100644
--- a/content.tex
+++ b/content.tex
@@ -2079,6 +2079,11 @@ \subsection{MMIO-specific Initialization And Device Operation}\label{sec:Virtio
\subsubsection{Device Initialization}\label{sec:Virtio Transport Options / Virtio Over MMIO / MMIO-specific Initialization And Device Operation / Device Initialization}
+\devicenormative{\paragraph}{Device Initialization}{Virtio Transport Options / Virtio Over MMIO / MMIO-specific Initialization And Device Operation / Device Initialization}
+
+Device MUST NOT set bit VIRTIO_F_ADMIN_VQ (bit 41) in
+DeviceFeatures.
+
\drivernormative{\paragraph}{Device Initialization}{Virtio Transport Options / Virtio Over MMIO / MMIO-specific Initialization And Device Operation / Device Initialization}
The driver MUST start the device initialization by reading and
@@ -2093,6 +2098,9 @@ \subsubsection{Device Initialization}\label{sec:Virtio Transport Options / Virti
Further initialization MUST follow the procedure described in
\ref{sec:General Initialization And Device Operation / Device Initialization}~\nameref{sec:General Initialization And Device Operation / Device Initialization}.
+Driver MUST NOT set bit VIRTIO_F_ADMIN_VQ (bit 41) in
+DriverFeatures even if offered by the device.
+
\subsubsection{Virtqueue Configuration}\label{sec:Virtio Transport Options / Virtio Over MMIO / MMIO-specific Initialization And Device Operation / Virtqueue Configuration}
The driver will typically initialize the virtual queue in the following way:
--
MST
next prev parent reply other threads:[~2022-08-12 17:19 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 17:18 [PATCH RFC v7 0/8] Introduce device group and device management Michael S. Tsirkin
2022-08-12 17:18 ` [PATCH RFC v7 1/8] Introduce device group Michael S. Tsirkin
2022-08-16 16:51 ` [virtio-comment] " Max Gurtovoy
2022-08-18 8:37 ` Jason Wang
2022-08-18 8:56 ` Michael S. Tsirkin
2022-08-12 17:19 ` [PATCH RFC v7 2/8] Introduce group administration commands Michael S. Tsirkin
2022-08-16 22:26 ` Max Gurtovoy
2022-08-18 8:46 ` [virtio-comment] " Jason Wang
2022-08-18 8:51 ` [virtio] " Michael S. Tsirkin
2022-08-19 0:26 ` Jason Wang
2022-08-19 3:28 ` Michael S. Tsirkin
2022-08-19 4:37 ` [virtio-comment] " Jason Wang
2022-08-19 23:41 ` Max Gurtovoy
2022-08-23 3:32 ` [virtio-comment] " Jason Wang
2022-08-24 9:20 ` Max Gurtovoy
2022-08-12 17:19 ` [PATCH RFC v7 3/8] Introduce virtio admin virtqueue Michael S. Tsirkin
2022-08-16 22:29 ` [virtio-comment] " Max Gurtovoy
2022-08-12 17:19 ` [PATCH RFC v7 4/8] Add admin_queue_index register to PCI common configuration structure Michael S. Tsirkin
2022-08-16 22:31 ` Max Gurtovoy
2022-08-18 8:49 ` Jason Wang
2022-08-18 8:52 ` Michael S. Tsirkin
2022-08-18 8:55 ` Max Gurtovoy
2022-08-19 0:28 ` Jason Wang
2022-08-19 3:50 ` Michael S. Tsirkin
2022-08-12 17:19 ` Michael S. Tsirkin [this message]
2022-08-12 17:19 ` [PATCH RFC v7 6/8] ccw: disallow ADMIN_VQ Michael S. Tsirkin
2022-08-16 14:48 ` [virtio] " Halil Pasic
2022-08-16 15:48 ` Michael S. Tsirkin
2022-08-16 15:50 ` Michael S. Tsirkin
2022-08-16 22:36 ` [virtio-comment] " Max Gurtovoy
2022-08-18 13:39 ` Halil Pasic
2022-08-19 3:57 ` Michael S. Tsirkin
2022-08-23 23:45 ` [virtio-dev] " Halil Pasic
2022-08-28 9:35 ` Michael S. Tsirkin
2022-08-31 14:33 ` [virtio] " Halil Pasic
2022-08-31 14:50 ` Michael S. Tsirkin
2022-09-01 23:33 ` Halil Pasic
2022-08-29 18:28 ` Michael S. Tsirkin
2022-08-30 12:48 ` Halil Pasic
2022-08-30 14:31 ` Cornelia Huck
2022-08-12 17:19 ` [PATCH RFC v7 7/8] admin: document that structures can be shorter or longer Michael S. Tsirkin
2022-08-16 22:53 ` [virtio-comment] " Max Gurtovoy
2022-08-12 17:19 ` [PATCH RFC v7 8/8] admin command list discovery Michael S. Tsirkin
2022-08-16 23:06 ` Max Gurtovoy
2022-08-18 8:51 ` Jason Wang
2022-08-18 8:54 ` Michael S. Tsirkin
2022-08-18 8:56 ` [virtio-dev] " Zhu, Lingshan
2022-08-18 9:05 ` 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=20220812171841.12183-6-mst@redhat.com \
--to=mst@redhat.com \
--cc=Piotr.Uminski@intel.com \
--cc=aadam@redhat.com \
--cc=cohuck@redhat.com \
--cc=eperezma@redhat.com \
--cc=hang.yuan@intel.com \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=mgurtovoy@nvidia.com \
--cc=nrupal.jani@intel.com \
--cc=oren@nvidia.com \
--cc=parav@nvidia.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