Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Zhu Lingshan <lingshan.zhu@intel.com>
To: 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-comment@lists.oasis-open.org,
	Zhu Lingshan <lingshan.zhu@intel.com>
Subject: [virtio-comment] [PATCH V3 RESEND 0/4] Introduce virtio transport virtqueue
Date: Fri,  5 Aug 2022 17:53:39 +0800	[thread overview]
Message-ID: <20220805095343.486546-1-lingshan.zhu@intel.com> (raw)

This series introduces virtio transport virtqueue as a new
transport layer for virtio devices.

This series defines the concepts of virtio management device
and virtio managed devices.

This series also defines a commands set over the transport virtqueue,
including:
The command to query available resources of the management device
The commands to create / destroy the managed devices.
The commands to config the managed devices.
The commands to config virtqueues of the managed devices.

Changes from V2:
1)Drop Feature bit VIRTIO_F_TRANSPT_VQ_MDEV (Michael)
2)Extend the feature bits to 128 bits as required in section 2.2 Feature Bits (Michael)
3)Explicit describes the feature bit VIRTIO_F_TRANSPT_VQ should be negotiated with the management device for the commands (Michael)
4)Removed MSI mask / unmask commands (Michael)
5)Add commands to get MSI entries of vqs and config space (Michael)
6)Add a description on the behaviors when disable a MSI (Michael)
7)Removed the section “Management device discovery” (Michael)
8)Remove pre-created managed devices, it is totally depending on the HW implementation (Michael)
9)Detailed descriptions for VIRITO DEVICE ID in the creation command (Michael)
10)Better device requirements for the device config space generation (Michael)
11)Re-use struct transportq_ctrl_packed_vq_state{} for both packed vq state set/get (Michael)

Changes form V1:
1)Add a command to set per-vq asid(Jason)
2)Add a command to reset a virtqueue(Jason)
3)Add support for packed virtqueue state(Jason)
4)Allow nested managed devices(Jason)
5)Provides device feature bits in the provisioning(Jason)
6)Removed most of the error codes, only left OK and ERR(Jason)
7)“virtual devices” is renamed to “managed devices”, to be more general(Jason)

Zhu Lingshan (4):
  Introduce virito transport virtqueue
  Introduce the commands set of the transport vq
  Describe the process to present a managed device
  Add transport vq number for virtio blk and net

 content.tex      | 760 +++++++++++++++++++++++++++++++++++++++++++++++
 introduction.tex |   3 +
 2 files changed, 763 insertions(+)

-- 
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-05 10:02 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  9:53 Zhu Lingshan [this message]
2022-08-05  9:53 ` [virtio-comment] [PATCH V3 RESEND 1/4] Introduce virito transport virtqueue Zhu Lingshan
2022-08-08  9:12   ` Jason Wang
2022-08-09  8:36     ` Zhu, Lingshan
2022-08-09  9:12       ` Michael S. Tsirkin
2022-08-09  9:19         ` Zhu, Lingshan
2022-08-09  9:21           ` Jason Wang
2022-08-09  9:28             ` Zhu, Lingshan
2022-08-09  9:31               ` Jason Wang
2022-08-09  9:35                 ` Michael S. Tsirkin
2022-08-09  9:37                   ` Jason Wang
2022-08-09  9:43                     ` Zhu, Lingshan
2022-08-09  9:33               ` Michael S. Tsirkin
2022-08-09  9:29           ` Michael S. Tsirkin
2022-08-09  9:43             ` Zhu, Lingshan
2022-08-09 20:57               ` Michael S. Tsirkin
2022-08-09  9:28         ` Jason Wang
2022-08-09 21:03           ` Michael S. Tsirkin
2022-08-10  7:41             ` Jason Wang
2022-08-10  9:04               ` Michael S. Tsirkin
2022-08-05  9:53 ` [virtio-comment] [PATCH V3 RESEND 2/4] Introduce the commands set of the transport vq Zhu Lingshan
2022-08-08 10:04   ` Jason Wang
2022-08-09 13:09     ` Zhu, Lingshan
2022-08-10  1:56       ` Jason Wang
2022-08-10  8:49         ` Zhu, Lingshan
2022-08-10 12:58           ` Michael S. Tsirkin
2022-08-16  5:55             ` Zhu, Lingshan
2022-08-16  6:21               ` Michael S. Tsirkin
2022-08-16  8:53                 ` Zhu, Lingshan
2022-08-10  9:34         ` Michael S. Tsirkin
2022-08-16  9:02           ` Zhu, Lingshan
2022-08-05  9:53 ` [virtio-comment] [PATCH V3 RESEND 3/4] Describe the process to present a managed device Zhu Lingshan
2022-08-05  9:53 ` [virtio-comment] [PATCH V3 RESEND 4/4] Add transport vq number for virtio blk and net 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=20220805095343.486546-1-lingshan.zhu@intel.com \
    --to=lingshan.zhu@intel.com \
    --cc=Piotr.Uminski@intel.com \
    --cc=cohuck@redhat.com \
    --cc=hang.yuan@intel.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox