From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
virtio-comment@lists.oasis-open.org, Greg Kurz <groug@kaod.org>,
Dominique Martinet <asmadeus@codewreck.org>
Subject: Re: [PATCH 1/2] Add VIRTIO_RING_F_INDIRECT_SIZE
Date: Mon, 24 Jan 2022 15:24:43 +0100 [thread overview]
Message-ID: <1969031.2ol2gXnArA@silver> (raw)
In-Reply-To: <877dapl1i8.fsf@redhat.com>
On Montag, 24. Januar 2022 14:14:07 CET Cornelia Huck wrote:
> On Mon, Jan 24 2022, Stefan Hajnoczi <stefanha@redhat.com> wrote:
> > On Tue, Dec 14, 2021 at 04:13:10PM +0100, Christian Schoenebeck wrote:
> >> This new feature flag allows to decouple the maximum amount of
> >> descriptors in indirect descriptor tables from the Queue Size.
> >>
> >> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/122
> >> Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> >> ---
Adding Dominique Martinet on CC from now on, for being informed about progress
on this virtio issue for Linux kernel side.
> >>
> >> content.tex | 21 +++++++++++++++++++++
> >> split-ring.tex | 2 +-
> >> 2 files changed, 22 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/content.tex b/content.tex
> >> index 5d112af..0aa4842 100644
> >> --- a/content.tex
> >> +++ b/content.tex
> >> @@ -6693,6 +6693,27 @@ \chapter{Reserved Feature Bits}\label{sec:Reserved
> >> Feature Bits}>>
> >> transport specific.
> >> For more details about driver notifications over PCI see
> >> \ref{sec:Virtio Transport Options / Virtio Over PCI Bus /
> >> PCI-specific Initialization And Device Operation / Available Buffer
> >> Notifications}.>>
> >> + \item[VIRTIO_RING_F_INDIRECT_SIZE(40)] This feature indicates that the
> >
> > Another feature bit was added in the meantime:
> > \item[VIRTIO_F_RING_RESET(40)] This feature indicates
> >
> > ^^
> >
> > Please use 41 and update the text that says:
> > \item[24 to 40] Feature bits reserved for extensions to the queue and
> > feature negotiation mechanisms
> >
> > \item[41 to 49, and 128 and above] Feature bits reserved for future
> > extensions.
Sure, I'll take care of that. As I am always rebasing to latest git version of
the spec, I guess I would have realized it anyway.
> Indeed... I'm wondering whether we could automate updating this with
> some clever variables?
Well, for LaTeX there is
\newcommand{\newCommandName}{1234}
and
\def\variable{1234}
Both solutions have pros and cons. But not sure I would want to rack my brain
on that. I just manually update the feature bit number for now :)
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2022-01-24 14:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 15:13 [PATCH 0/2] Add VIRTIO_RING_F_INDIRECT_SIZE and queue_indirect_size Christian Schoenebeck
2021-12-14 15:13 ` [PATCH 1/2] Add VIRTIO_RING_F_INDIRECT_SIZE Christian Schoenebeck
2021-12-14 16:59 ` [virtio-comment] " Cornelia Huck
2021-12-14 18:28 ` Christian Schoenebeck
2021-12-23 10:54 ` Cornelia Huck
2022-01-24 13:08 ` Stefan Hajnoczi
2022-01-24 13:14 ` [virtio-comment] " Cornelia Huck
2022-01-24 14:24 ` Christian Schoenebeck [this message]
2021-12-14 15:13 ` [PATCH 2/2] Add common configuration field "queue_indirect_size" Christian Schoenebeck
2021-12-14 17:20 ` [virtio-comment] " Cornelia Huck
2021-12-15 13:59 ` Christian Schoenebeck
2021-12-23 11:03 ` [virtio-comment] " Cornelia Huck
2021-12-29 14:16 ` Christian Schoenebeck
2022-01-03 13:21 ` [virtio-comment] " Cornelia Huck
2022-01-05 13:52 ` Christian Schoenebeck
2022-01-24 13:39 ` [virtio-comment] " Stefan Hajnoczi
2022-01-24 14:31 ` Christian Schoenebeck
2022-01-24 16:41 ` Stefan Hajnoczi
2022-01-25 19:05 ` Christian Schoenebeck
2022-01-26 10:01 ` Stefan Hajnoczi
2022-01-24 13:53 ` Stefan Hajnoczi
2022-02-19 16:36 ` Christian Schoenebeck
2022-02-21 10:33 ` Stefan Hajnoczi
2022-02-21 13:28 ` Christian Schoenebeck
2022-01-24 13:54 ` [PATCH 0/2] Add VIRTIO_RING_F_INDIRECT_SIZE and queue_indirect_size 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=1969031.2ol2gXnArA@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