All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Zhu Lingshan <lingshan.zhu@intel.com>
Cc: jasowang@redhat.com, cohuck@redhat.com, sgarzare@redhat.com,
	stefanha@redhat.com, nrupal.jani@intel.com,
	Piotr.Uminski@intel.com, virtio-comment@lists.oasis-open.org
Subject: [virtio-comment] Re: [PATCH V2 2/5] Introduce feature bit VIRTIO_F_TRANSPT_VQ_MDEV
Date: Mon, 1 Aug 2022 16:27:32 -0400	[thread overview]
Message-ID: <20220801162534-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220801093216.362119-3-lingshan.zhu@intel.com>

On Mon, Aug 01, 2022 at 05:32:13PM +0800, Zhu Lingshan wrote:
> This commit introduces feature bit VIRTIO_F_TRANSPT_VQ_MDEV,
> which depends on VIRTIO_F_TRANSPT_VQ.
> 
> Feature bit VIRTIO_F_TRANSPT_VQ_MDEV indicates that the managed
> devices are created, configured and destroyed through the
> transport virtqueue, the transport virtqueue is the
> transport layer for the managed devices.

I'd avoid the term MDEV if possible, it's already used in virt contexts.


> Signed-off-by: Jason Wang <jasowang@redhat.com>
> Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
> ---
>  content.tex | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/content.tex b/content.tex
> index 969ca46..143949e 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -2968,6 +2968,18 @@ \subsection{Managed Devices Dscovery}\label{sec:Virtio Transport Options /Virtio
>  
>  Managed devices are created and discovered through a transport virtqueue.
>  
> +\subsection{Transport Virtqueue Features}\label{sec:Virtio Transport Options /Virtio Over Transport Virtqueue / Transport Virtqueue Features}
> +
> +Feature bit VIRTIO_F_TRANSPT_VQ_MDEV indicates that the managed devices are created, configured
> +and destroyed through the transport virtqueue.

Feature bit being present where? On the management device?

> +This means the transport virtqueue is the transport layer for the managed devices.

confused. how does this differ from VIRTIO_F_TRANSPT_VQ?

> +
> +Feature bit VIRTIO_F_TRANSPT_VQ_MDEV depends on VIRTIO_F_TRANSPT_VQ
> +
> +\devicenormative{\subsubsection}{Transport Virtqueue Features}{Virtio Transport Options / Virtio Over Transport Virtqueue / Transport Virtqueue Features}
> +
> +The management device MUST not accept VIRTIO_F_TRANSPT_VQ_MDEV if VIRTIO_F_TRANSPT_VQ is not negotiated.
> +
>  \chapter{Device Types}\label{sec:Device Types}
>  
>  On top of the queues, config space and feature negotiation facilities
> -- 
> 2.35.3


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/


  reply	other threads:[~2022-08-01 20:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01  9:32 [PATCH V2 0/5] Introduce virtio transport virtqueue Zhu Lingshan
2022-08-01  9:32 ` [PATCH V2 1/5] Introduce virito " Zhu Lingshan
2022-08-01 20:25   ` Michael S. Tsirkin
2022-08-02  2:54     ` Zhu, Lingshan
2022-08-01  9:32 ` [PATCH V2 2/5] Introduce feature bit VIRTIO_F_TRANSPT_VQ_MDEV Zhu Lingshan
2022-08-01 20:27   ` Michael S. Tsirkin [this message]
2022-08-02  3:17     ` [virtio-comment] " Zhu, Lingshan
2022-08-02  6:32       ` Zhu, Lingshan
2022-08-02  6:52       ` Michael S. Tsirkin
2022-08-02 11:54         ` Zhu, Lingshan
2022-08-02 12:55           ` Michael S. Tsirkin
2022-08-02 13:15             ` Zhu, Lingshan
2022-08-02 13:20               ` Michael S. Tsirkin
2022-08-02 13:32                 ` Zhu, Lingshan
2022-08-02 13:37                 ` Zhu, Lingshan
2022-08-01  9:32 ` [PATCH V2 3/5] Introduce the commands set of the transport vq Zhu Lingshan
2022-08-01 20:53   ` Michael S. Tsirkin
2022-08-02 13:07     ` [virtio-comment] " Zhu, Lingshan
2022-08-01  9:32 ` [PATCH V2 4/5] Describe the process to present a managed device Zhu Lingshan
2022-08-01  9:32 ` [PATCH V2 5/5] Add transport vq number for virtio blk and net Zhu Lingshan
2022-08-01 20:54   ` Michael S. Tsirkin
2022-08-01  9:48 ` [PATCH V2 0/5] Introduce virtio transport virtqueue Michael S. Tsirkin
2022-08-01 20:56 ` Michael S. Tsirkin
2022-08-02 13:18   ` [virtio-comment] " Zhu, Lingshan
2022-08-02 13:21   ` Zhu, Lingshan

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=20220801162534-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=Piotr.Uminski@intel.com \
    --cc=cohuck@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=lingshan.zhu@intel.com \
    --cc=nrupal.jani@intel.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-comment@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 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.