From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: virtio-comment@lists.oasis-open.org
Cc: Cornelia Huck <cohuck@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>, Greg Kurz <groug@kaod.org>,
Dominique Martinet <asmadeus@codewreck.org>
Subject: [virtio-comment] [PATCH v2 0/4] Add VIRTIO_RING_F_INDIRECT_SIZE and queue_indirect_size
Date: Mon, 21 Feb 2022 17:22:18 +0100 [thread overview]
Message-ID: <2255414.aXzeqRvSCW@silver> (raw)
This is a follow-up of:
[1/2]: https://lists.oasis-open.org/archives/virtio-comment/202112/msg00034.html
[2/2]: https://lists.oasis-open.org/archives/virtio-comment/202112/msg00035.html
These 4 patches introduce a more fine graded control over the maximum length
of indirect descriptor tables.
Associated Github Task:
https://github.com/oasis-tcs/virtio-spec/issues/122
Latest Version (all patches):
https://github.com/cschoenebeck/virtio-spec/commits/long_indirect_descr
v1 -> v2:
* Update reserved bits section [patch 1].
* Add requirement to device normative section [patch 1].
* Use the general new term "Queue Indirect Size" where possible instead of
mentioning a bus specific field name [patch 1].
* Simplified phrasing of requirements in split ring section [patch 1].
* Move bus-independent changes from patch 2 to patch 1.
* There is only one indirect descriptor table allowed per buffer
(round-trip message), so use the term "per indirect descriptor table" for
the semantic of "Queue Indirect Size" in patch 2.
* Simplify phrasing of requirements in patch 2.
* MMIO: First shot [NEW patch 3].
* CCW: First shot [NEW patch 4].
Christian Schoenebeck (4):
Add VIRTIO_RING_F_INDIRECT_SIZE
Add PCI configuration field "queue_indirect_size"
Add MMIO configuration register "QueueIndirectNum"
Add CCW configuration field "indirect_num" to vq_info_block
content.tex | 77 ++++++++++++++++++++++++++++++++++++++++++++++---
packed-ring.tex | 2 +-
split-ring.tex | 8 +++--
3 files changed, 80 insertions(+), 7 deletions(-)
--
2.30.2
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/
next reply other threads:[~2022-02-21 16:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 16:22 Christian Schoenebeck [this message]
2022-02-21 16:25 ` [virtio-comment] [PATCH v2 1/4] Add VIRTIO_RING_F_INDIRECT_SIZE Christian Schoenebeck
2022-03-10 14:57 ` Stefan Hajnoczi
2022-03-10 16:20 ` Christian Schoenebeck
2022-02-21 16:27 ` [PATCH v2 2/4] Add PCI configuration field "queue_indirect_size" Christian Schoenebeck
2022-03-10 15:04 ` [virtio-comment] " Stefan Hajnoczi
2022-02-21 16:58 ` [PATCH v2 3/4] Add MMIO configuration register "QueueIndirectNum" Christian Schoenebeck
2022-03-10 15:23 ` Stefan Hajnoczi
2022-02-21 17:01 ` [PATCH v2 4/4] Add CCW configuration field "indirect_num" to vq_info_block Christian Schoenebeck
2022-03-10 15:26 ` Stefan Hajnoczi
2022-03-10 16:09 ` [virtio-comment] " Cornelia Huck
2022-03-11 8:53 ` Christian Schoenebeck
2022-03-11 9:21 ` [virtio-comment] " Cornelia Huck
2022-03-11 11:15 ` Halil Pasic
2022-03-11 12:09 ` [virtio-comment] " Christian Schoenebeck
2022-03-10 16:09 ` Christian Schoenebeck
2022-03-09 14:58 ` [virtio-comment] [PATCH v2 0/4] Add VIRTIO_RING_F_INDIRECT_SIZE and queue_indirect_size Christian Schoenebeck
2022-03-10 15:35 ` Stefan Hajnoczi
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=2255414.aXzeqRvSCW@silver \
--to=qemu_oss@crudebyte.com \
--cc=asmadeus@codewreck.org \
--cc=cohuck@redhat.com \
--cc=groug@kaod.org \
--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