From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, jasowang@redhat.com,
mst@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>,
pasic@linux.ibm.com, Shahaf Shuler <shahafs@nvidia.com>,
Parav Pandit <parav@nvidia.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [virtio] Re: [PATCH v8 7/9] ccw: document ADMIN_VQ as reserved
Date: Mon, 21 Nov 2022 16:53:22 +0100 [thread overview]
Message-ID: <87r0xw5mod.fsf@redhat.com> (raw)
In-Reply-To: <20221121012419.317406-8-mst@redhat.com>
On Sun, Nov 20 2022, "Michael S. Tsirkin" <mst@redhat.com> 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>
> ---
> content.tex | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/content.tex b/content.tex
> index 9c74fa9..7111929 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -2971,6 +2971,18 @@ \subsubsection{Resetting Devices}\label{sec:Virtio Transport Options / Virtio ov
> MAY also choose to verify reset completion by reading \field{device status} via
> CCW_CMD_READ_STATUS and checking whether it is 0 afterwards.
>
> +\subsection{Features reserved for future use}\label{sec:Virtio Transport Options / Virtio Over MMIO / Features reserved for future use}
s/MMIO/Channel I/O/
> +
> +At this time, devices and drivers utilizing Virtio over channel I/O
> +do not support the following features:
> +\begin{itemize}
> +
> +\item VIRTIO_F_ADMIN_VQ
There are already a few features not yet supported for ccw (queue reset,
shared memory, ...) -- would it make sense to add a separate patch
listing all of the features not yet supported prior to adding all of the
admin vq infrastructure? Otherwise, this section is a bit misleading.
(What is the situation for MMIO?)
> +
> +\end{itemize}
> +
> +These features are reserved for future use.
> +
> \chapter{Device Types}\label{sec:Device Types}
>
> On top of the queues, config space and feature negotiation facilities
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
next prev parent reply other threads:[~2022-11-21 15:53 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 1:25 [PATCH v8 0/9] Introduce device group and device management Michael S. Tsirkin
2022-11-21 1:25 ` [PATCH v8 1/9] virtio: document forward compatibility guarantees Michael S. Tsirkin
2022-11-21 15:24 ` [virtio] " Cornelia Huck
2022-11-22 20:26 ` Michael S. Tsirkin
2022-11-23 9:21 ` [virtio-dev] " Cornelia Huck
2022-11-23 9:28 ` Michael S. Tsirkin
2022-11-21 1:25 ` [PATCH v8 2/9] admin: introduce device group and related concepts Michael S. Tsirkin
2022-11-22 12:11 ` [virtio] " Cornelia Huck
2022-11-22 20:17 ` Michael S. Tsirkin
2022-11-23 9:26 ` [virtio-comment] " Cornelia Huck
2022-11-21 1:25 ` [PATCH v8 3/9] admin: introduce group administration commands Michael S. Tsirkin
2022-11-22 12:43 ` [virtio-dev] " Cornelia Huck
2022-11-21 1:25 ` [PATCH v8 4/9] admin: introduce virtio admin virtqueues Michael S. Tsirkin
2022-11-22 13:14 ` [virtio-comment] " Cornelia Huck
2022-11-22 19:31 ` Michael S. Tsirkin
2022-11-23 9:30 ` [virtio-dev] " Cornelia Huck
2022-11-23 9:32 ` Michael S. Tsirkin
2022-11-23 9:54 ` [virtio-dev] " Cornelia Huck
2022-11-21 1:25 ` [PATCH v8 5/9] pci: add admin vq registers to virtio over pci Michael S. Tsirkin
2022-11-22 14:46 ` [virtio-dev] " Cornelia Huck
2022-11-22 19:23 ` Michael S. Tsirkin
2022-11-23 9:36 ` [virtio-comment] " Cornelia Huck
2022-11-23 9:38 ` Michael S. Tsirkin
2022-11-21 1:25 ` [PATCH v8 6/9] mmio: document ADMIN_VQ as reserved Michael S. Tsirkin
2022-11-21 1:25 ` [PATCH v8 7/9] ccw: " Michael S. Tsirkin
2022-11-21 15:53 ` Cornelia Huck [this message]
2022-11-21 16:48 ` Michael S. Tsirkin
2022-11-21 17:09 ` Michael S. Tsirkin
2022-11-22 8:50 ` [virtio-dev] " Cornelia Huck
2022-11-22 9:51 ` Michael S. Tsirkin
2022-11-21 1:25 ` [PATCH v8 8/9] admin: command list discovery Michael S. Tsirkin
2022-11-21 11:06 ` Uminski, Piotr
2022-12-15 9:09 ` [virtio-comment] " Michael S. Tsirkin
2022-12-15 9:52 ` Uminski, Piotr
2022-12-24 18:17 ` Michael S. Tsirkin
2022-11-22 15:25 ` [virtio] " Cornelia Huck
2022-11-22 19:17 ` Michael S. Tsirkin
2022-11-23 9:51 ` [virtio] " Cornelia Huck
2022-11-23 10:00 ` Michael S. Tsirkin
2022-11-23 10:09 ` [virtio] " Cornelia Huck
2022-11-23 10:16 ` Michael S. Tsirkin
2022-11-23 10:33 ` [virtio] " Cornelia Huck
2022-11-23 11:21 ` Michael S. Tsirkin
2022-11-21 1:25 ` [PATCH v8 9/9] admin: conformance clauses Michael S. Tsirkin
2022-11-22 16:06 ` [virtio] " Cornelia Huck
2022-11-22 19:20 ` Michael S. Tsirkin
2022-11-23 9:52 ` [virtio-dev] " 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=87r0xw5mod.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=Piotr.Uminski@intel.com \
--cc=hang.yuan@intel.com \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=mgurtovoy@nvidia.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