From: Alexander Duyck <alexander.duyck@gmail.com>
To: cohuck@redhat.com, david@redhat.com, mst@redhat.com
Cc: virtio-dev@lists.oasis-open.or, virtio-comment@lists.oasis-open.org
Subject: [PATCH RFC 0/3] virtio-spec: Add documentation for recently added balloon features
Date: Wed, 29 Apr 2020 10:27:15 -0700 [thread overview]
Message-ID: <20200429172634.457.40167.stgit@localhost.localdomain> (raw)
This patch set is meant to add documentation for balloon features that have
been recently added to the Linux kernel[1,2] and that we are currently
working on adding to QEMU[3].
I am submitting them as an RFC as it has been a while since I have written
any requirements or specification documents, so my wording on things will
likely need some updates. In addition I have not before submitted
virtio-spec updates. As such I would appreciate information on if this is
the correct process for updating the document, or if I need to take some
other/additional steps.
[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
content.tex | 232 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 229 insertions(+), 3 deletions(-)
--
next reply other threads:[~2020-04-29 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 17:27 Alexander Duyck [this message]
2020-04-29 17:27 ` [PATCH RFC 1/3] content: Document balloon feature free page hints Alexander Duyck
2020-04-29 17:27 ` [PATCH RFC 2/3] content: Document balloon feature page poison Alexander Duyck
2020-04-29 17:27 ` [PATCH RFC 3/3] content: Document balloon feature free page reporting Alexander Duyck
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=20200429172634.457.40167.stgit@localhost.localdomain \
--to=alexander.duyck@gmail.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.or \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.