public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: 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, 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>,
	Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [virtio-dev] Re: [virtio-comment] Re: [PATCH v11 06/10] mmio: document ADMIN_VQ as reserved
Date: Mon, 24 Apr 2023 11:38:56 -0400	[thread overview]
Message-ID: <20230424113729-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <8f9df843-247c-df96-bae5-4e4c2b2d1e8e@nvidia.com>

On Mon, Apr 03, 2023 at 11:54:04AM -0400, Parav Pandit wrote:
> 
> 
> On 4/3/2023 11:03 AM, 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>
> > ---
> >   content.tex | 12 ++++++++++++
> >   1 file changed, 12 insertions(+)
> > 
> > diff --git a/content.tex b/content.tex
> > index 5057df2..f7446bf 100644
> > --- a/content.tex
> > +++ b/content.tex
> > @@ -2364,6 +2364,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}
> > +
> > +At this time, devices and drivers utilizing Virtio Over MMIO
> No need to mention, "At this time".
> It is always spec version to version.
> And "current time" of the spec is visible in its version.
> Please remove "At this time".
> 
> > +do not support the following features:
> > +\begin{itemize}
> > +
> > +\item VIRTIO_F_ADMIN_VQ
> > +
> > +\end{itemize}
> > +
> > +These features are reserved for future use.
> > +
> Above line should be moved up before listing the features.
> or should be written as
> s/These/Above
> 
> like, Above listed features are reserved for future use.

I don't feel it matters. And
we were asked to reduce the use of "below" and "above" in new text
as disrespectful to people using screen readers and such.

> >   \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
> 
> Reviewed-by: Parav Pandit <parav@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/
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2023-04-24 15:39 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   ` [virtio-dev] " Stefan Hajnoczi
2023-04-06  4:14   ` 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     ` Michael S. Tsirkin [this message]
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=20230424113729-mutt-send-email-mst@kernel.org \
    --to=mst@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=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