From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
virtio-comment@lists.oasis-open.org,
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
Cc: 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>
Subject: [virtio-comment] Re: [PATCH v12 06/10] mmio: document ADMIN_VQ as reserved
Date: Tue, 25 Apr 2023 01:08:39 +0300 [thread overview]
Message-ID: <66eb18c8-506b-b5a2-69a4-7cfaf7ae702e@nvidia.com> (raw)
In-Reply-To: <a67ae1170d9535a98862d01825b2662180d77d82.1682354275.git.mst@redhat.com>
On 24/04/2023 19:44, Michael S. Tsirkin wrote:
> Adding relevant registers needs more work and it's not
> clear what the use-case will be as currently only
> the PCI transport is supported. But let's keep the
> door open on this.
> We already say it's reserved in a central place, but it
> does not hurt to remind implementers to mask it.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> Reviewed-by: Parav Pandit <parav@nvidia.com>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
>
> ---
>
> changes in v12:
> drop "as of now" to address comment by parav
> ---
> content.tex | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/content.tex b/content.tex
> index bcbc06d..7d6d9c4 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -2365,6 +2365,18 @@ \subsection{Legacy interface}\label{sec:Virtio Transport Options / Virtio Over M
>
> 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.
> +
> \section{Virtio Over Channel I/O}\label{sec:Virtio Transport Options / Virtio Over Channel I/O}
>
> S/390 based virtual machines support neither PCI nor MMIO, so a
Looks good,
Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2023-04-24 22:09 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 16:44 [virtio-comment] [PATCH v12 00/10] Introduce device group and device management Michael S. Tsirkin
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 01/10] virtio: document forward compatibility guarantees Michael S. Tsirkin
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 02/10] admin: introduce device group and related concepts Michael S. Tsirkin
2023-04-24 21:02 ` [virtio-comment] " Max Gurtovoy
2023-04-24 21:47 ` Parav Pandit
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 03/10] admin: introduce group administration commands Michael S. Tsirkin
2023-04-24 21:29 ` [virtio-comment] " Max Gurtovoy
2023-04-24 21:33 ` Michael S. Tsirkin
2023-04-24 22:07 ` Parav Pandit
2023-04-25 6:20 ` Michael S. Tsirkin
2023-04-25 13:25 ` [virtio-comment] " Parav Pandit
2023-04-25 13:31 ` [virtio-comment] " Michael S. Tsirkin
2023-04-25 13:38 ` [virtio-comment] " Parav Pandit
2023-04-25 20:04 ` [virtio-comment] " Michael S. Tsirkin
2023-04-25 20:18 ` [virtio-comment] " Parav Pandit
2023-04-25 20:55 ` [virtio-comment] " Michael S. Tsirkin
2023-04-26 18:18 ` Parav Pandit
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 04/10] admin: introduce virtio admin virtqueues Michael S. Tsirkin
2023-04-24 22:32 ` [virtio-comment] " Parav Pandit
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 05/10] pci: add admin vq registers to virtio over pci Michael S. Tsirkin
2023-04-24 22:06 ` [virtio-comment] " Max Gurtovoy
2023-04-24 22:14 ` Parav Pandit
2023-04-26 21:12 ` Max Gurtovoy
2023-04-26 22:11 ` [virtio-comment] " Parav Pandit
2023-04-26 22:31 ` [virtio-comment] " Max Gurtovoy
2023-04-27 0:11 ` [virtio-comment] " Parav Pandit
2023-05-05 15:12 ` [virtio-comment] " Michael S. Tsirkin
2023-05-05 15:14 ` [virtio-comment] " Parav Pandit
2023-04-27 17:57 ` [virtio-comment] " Michael S. Tsirkin
2023-04-27 18:50 ` Max Gurtovoy
2023-05-05 15:22 ` Michael S. Tsirkin
2023-05-05 15:25 ` [virtio-comment] " Parav Pandit
2023-04-24 22:29 ` [virtio-comment] " Parav Pandit
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 06/10] mmio: document ADMIN_VQ as reserved Michael S. Tsirkin
2023-04-24 22:08 ` Max Gurtovoy [this message]
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 07/10] ccw: " Michael S. Tsirkin
2023-04-24 22:09 ` [virtio-comment] " Max Gurtovoy
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 08/10] admin: command list discovery Michael S. Tsirkin
2023-04-24 22:27 ` [virtio-comment] " Parav Pandit
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 09/10] admin: conformance clauses Michael S. Tsirkin
2023-04-24 16:44 ` [virtio-comment] [PATCH v12 10/10] ccw: document more reserved features Michael S. Tsirkin
2023-04-24 22:17 ` [virtio-comment] " Parav Pandit
2023-04-24 21:34 ` [virtio-comment] Re: [PATCH v12 00/10] Introduce device group and device management Parav Pandit
2023-05-02 7:51 ` [virtio-comment] Re: [virtio] " David Edmondson
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=66eb18c8-506b-b5a2-69a4-7cfaf7ae702e@nvidia.com \
--to=mgurtovoy@nvidia.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=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