From: Cornelia Huck <cohuck@redhat.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
David Hildenbrand <david@redhat.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, "Wang,
Wei W" <wei.w.wang@intel.com>
Subject: [virtio-comment] Re: [PATCH v6 0/3] virtio-spec: Add documentation for recently added balloon features
Date: Mon, 10 Aug 2020 19:06:15 +0200 [thread overview]
Message-ID: <20200810190615.2613a258.cohuck@redhat.com> (raw)
In-Reply-To: <CAKgT0UchESZRMO2x6jK9u3qzEjb83eNnTm-XO9htpsRv-JF+3w@mail.gmail.com>
On Mon, 10 Aug 2020 09:58:38 -0700
Alexander Duyck <alexander.duyck@gmail.com> wrote:
> So it has been almost a month since I submitted this and there hasn't
> been any feedback. I'm wondering if this is ready for acceptance. If
> so what are the next steps to getting this accepted into the virtio
> spec?
It would be nice to get an ack on patch 1, but I don't feel comfortable
doing that.
The usual procedure is to request a vote (open a github issue, link to
the patch and mention the issue here, and request a vote in the issue.)
>
> Thanks.
>
> - Alex
>
> On Mon, Jul 13, 2020 at 11:24 AM Alexander Duyck
> <alexander.duyck@gmail.com> wrote:
> >
> > This patch set is meant to add documentation for balloon features that have
> > been recently added to the Linux kernel[1,2] and that were recently added
> > to QEMU[3].
> >
> > Changes since RFC:
> > Incorporated suggestions from Cornelia Huck
> > Fixed a few additional spelling errors
> >
> > Changes since v1:
> > Incorporated additional suggestions from Cornelia Huck
> > Dropped documentation referring to free page reporting from page poison patch
> >
> > Changes since v2:
> > Rewrote multiple statements based on input from David Hildenbrand
> > Dropped use of balloon and deflate from page hinting description
> > Dropped use of free page reporting from page poison description
> > Cleaned up several spots that didn't match RFC2119 style comments
> > Added conformance links.
> > Various other clean-ups.
> > Updated balloon command IDs based on input from Cornelia Huck
> >
> > Changes since v3:
> > Reordered patches to place free page hinting at end of patch set
> > Moved contents out of patch to poison and free page reporting patches
> > Updated patch description to document some known issues with feature
> > Further clean-ups based on input from David Hildenbrand
> >
> > Changes since v4:
> > Further clean-ups for page hinting based on input from David Hildenbrand
> >
> > Changes since v5:
> > Reverted patcher order changes from v3 placing hinting as first patch
> > Addressed comments and added Reviewed-by from Cornelia Huck
> > Addressed further items I found in free page hinting
> > Added requirement that output buffers be 4 bytes in size
> > Replaced reference to descriptor with buffer
> > Replaced references to free_page_hint_vq with free_page_vq
> >
> > [1]: https://lore.kernel.org/lkml/20200211224416.29318.44077.stgit@localhost.localdomain/
> > [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b0c504f154718904ae49349147e3b7e6ae91ffdc
> > [3]: https://lists.oasis-open.org/archives/virtio-dev/202004/msg00180.html
> >
> > ---
> >
> > Alexander Duyck (3):
> > content: Document balloon feature free page hints
> > content: Document balloon feature page poison
> > content: Document balloon feature free page reporting
> >
> >
> > conformance.tex | 6 +
> > content.tex | 279 ++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> > 2 files changed, 279 insertions(+), 6 deletions(-)
> >
> > --
> >
>
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/
prev parent reply other threads:[~2020-08-10 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 18:24 [virtio-comment] [PATCH v6 0/3] virtio-spec: Add documentation for recently added balloon features Alexander Duyck
2020-07-13 18:24 ` [virtio-comment] [PATCH v6 1/3] content: Document balloon feature free page hints Alexander Duyck
2020-07-13 18:24 ` [virtio-comment] [PATCH v6 2/3] content: Document balloon feature page poison Alexander Duyck
2020-07-13 18:24 ` [virtio-comment] [PATCH v6 3/3] content: Document balloon feature free page reporting Alexander Duyck
2020-08-10 16:58 ` [virtio-comment] Re: [PATCH v6 0/3] virtio-spec: Add documentation for recently added balloon features Alexander Duyck
2020-08-10 17:06 ` Cornelia Huck [this message]
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=20200810190615.2613a258.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=wei.w.wang@intel.com \
/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