From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, 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@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: [PATCH v8 0/9] Introduce device group and device management
Date: Sun, 20 Nov 2022 20:25:15 -0500 [thread overview]
Message-ID: <20221121012419.317406-1-mst@redhat.com> (raw)
This is out of RFC, since we have two commands which are useful
to discover supported group types (ATM can be none or SR-IOV).
Change log:
since v7:
make high level error codes match linux, with virtio specific codes
in a separate field
renamed _ACCEPT to _USE since that's what it does
clarified forward compatibility and non pci transports
support multiple admin vqs
conformance statements
lots of changes all over the place to I changed author from Max
to myself. Don't need to take credit but also don't want
to blame Max for my mistakes.
since v6:
- removed some extentions intended for future use.
We'll do them when we get there.
- brought back command list query from v5 in a simplified form -
it's here to address the case where a single parent
can address multiple groups, such as PF addressing
transport vq and sriov vfs.
- attempt to make terminology more formal.
In particular a term for whoever controls the group.
I am still going back
and forth between "parent" and "owner" - owner might
be better after all since it will work if we ever
have a self group. For now it's parent.
TODO (maybe?) - probably ok to defer until this part is upstream:
Add "all members" member id.
Add commands for MSI, feature discovery.
Add commands for transport vq.
My intent is to try and support both SR-IOV and SIOV
usecases with the same structure and maybe even the same
VQ.
For example, it might make sense to split creating/destroying
SIOV devices from the transport passing data from the guest - the
driver would then not negotiate VIRTIO_F_SR_IOV (which
then means auto-provisioning).
Michael S. Tsirkin (9):
virtio: document forward compatibility guarantees
admin: introduce device group and related concepts
admin: introduce group administration commands
admin: introduce virtio admin virtqueues
pci: add admin vq registers to virtio over pci
mmio: document ADMIN_VQ as reserved
ccw: document ADMIN_VQ as reserved
admin: command list discovery
admin: conformance clauses
admin.tex | 403 ++++++++++++++++++++++++++++++++++++++++++++++++++++
content.tex | 103 +++++++++++++-
2 files changed, 504 insertions(+), 2 deletions(-)
create mode 100644 admin.tex
--
MST
next reply other threads:[~2022-11-21 1:25 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 1:25 Michael S. Tsirkin [this message]
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 ` [virtio] " Cornelia Huck
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=20221121012419.317406-1-mst@redhat.com \
--to=mst@redhat.com \
--cc=Piotr.Uminski@intel.com \
--cc=cohuck@redhat.com \
--cc=hang.yuan@intel.com \
--cc=jasowang@redhat.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