From: "Michael S. Tsirkin" <mst@redhat.com>
To: Liang Li <liang.z.li@intel.com>
Cc: linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, linux-mm@kvack.org,
virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org,
qemu-devel@nongnu.org, quintela@redhat.com, dgilbert@redhat.com,
dave.hansen@intel.com, pbonzini@redhat.com,
cornelia.huck@de.ibm.com, amit.shah@redhat.com
Subject: Re: [Qemu-devel] [RESEND PATCH v3 kernel 6/7] virtio-balloon: define feature bit and head for misc virt queue
Date: Thu, 27 Oct 2016 21:29:38 +0300 [thread overview]
Message-ID: <20161027211928-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1477031080-12616-7-git-send-email-liang.z.li@intel.com>
On Fri, Oct 21, 2016 at 02:24:39PM +0800, Liang Li wrote:
> Define a new feature bit which supports a new virtual queue. This
> new virtual qeuque is for information exchange between hypervisor
> and guest. The VMM hypervisor can make use of this virtual queue
> to request the guest do some operations, e.g. drop page cache,
> synchronize file system, etc.
Can we call this something more informative pls?
host request vq?
> And the VMM hypervisor can get some
> of guest's runtime information through this virtual queue, e.g. the
> guest's unused page information, which can be used for live migration
> optimization.
I guess the idea is that guest gets requests from host and
then responds to them on this vq. Pls document.
>
> Signed-off-by: Liang Li <liang.z.li@intel.com>
> Cc: Michael S. Tsirkin <mst@redhat.com>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
> Cc: Amit Shah <amit.shah@redhat.com>
> ---
> include/uapi/linux/virtio_balloon.h | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/include/uapi/linux/virtio_balloon.h b/include/uapi/linux/virtio_balloon.h
> index d3b182a..3a9d633 100644
> --- a/include/uapi/linux/virtio_balloon.h
> +++ b/include/uapi/linux/virtio_balloon.h
> @@ -35,6 +35,7 @@
> #define VIRTIO_BALLOON_F_STATS_VQ 1 /* Memory Stats virtqueue */
> #define VIRTIO_BALLOON_F_DEFLATE_ON_OOM 2 /* Deflate balloon on OOM */
> #define VIRTIO_BALLOON_F_PAGE_BITMAP 3 /* Send page info with bitmap */
> +#define VIRTIO_BALLOON_F_MISC_VQ 4 /* Misc info virtqueue */
>
> /* Size of a PFN in the balloon interface. */
> #define VIRTIO_BALLOON_PFN_SHIFT 12
> @@ -101,4 +102,25 @@ struct balloon_bmap_hdr {
> __virtio64 bmap_len;
> };
>
> +enum balloon_req_id {
> + /* Get unused pages information */
unused page information
> + BALLOON_GET_UNUSED_PAGES,
> +};
> +
> +enum balloon_flag {
> + /* Have more data for a request */
> + BALLOON_FLAG_CONT,
> + /* No more data for a request */
> + BALLOON_FLAG_DONE,
> +};
is this a bit number or a value? Pls name consistently.
> +
> +struct balloon_req_hdr {
> + /* Used to distinguish different request */
requests
> + __virtio16 cmd;
> + /* Reserved */
> + __virtio16 reserved[3];
> + /* Request parameter */
> + __virtio64 param;
> +};
> +
> #endif /* _LINUX_VIRTIO_BALLOON_H */
Prefix structs with virtio_ as well pls.
Also, wouldn't it simplify code if we use __le for new structs?
> --
> 1.8.3.1
next prev parent reply other threads:[~2016-10-27 18:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 6:24 [Qemu-devel] [RESEND PATCH v3 kernel 0/7] Extend virtio-balloon for fast (de)inflating & fast live migration Liang Li
2016-10-21 6:24 ` [Qemu-devel] [RESEND PATCH v3 kernel 1/7] virtio-balloon: rework deflate to add page to a list Liang Li
2016-10-24 16:46 ` Dave Hansen
2016-10-25 1:14 ` Li, Liang Z
2016-10-21 6:24 ` [Qemu-devel] [RESEND PATCH v3 kernel 2/7] virtio-balloon: define new feature bit and page bitmap head Liang Li
2016-10-24 16:51 ` Dave Hansen
2016-10-25 1:21 ` Li, Liang Z
2016-10-26 15:35 ` Michael S. Tsirkin
2016-10-21 6:24 ` [Qemu-devel] [RESEND PATCH v3 kernel 3/7] mm: add a function to get the max pfn Liang Li
2016-10-24 16:53 ` Dave Hansen
2016-10-25 1:24 ` Li, Liang Z
2016-10-21 6:24 ` [Qemu-devel] [RESEND PATCH v3 kernel 4/7] virtio-balloon: speed up inflate/deflate process Liang Li
2016-10-25 6:36 ` Michael S. Tsirkin
2016-10-25 9:46 ` Li, Liang Z
2016-10-21 6:24 ` [Qemu-devel] [RESEND PATCH v3 kernel 5/7] mm: add the related functions to get unused page Liang Li
2016-10-21 6:24 ` [Qemu-devel] [RESEND PATCH v3 kernel 6/7] virtio-balloon: define feature bit and head for misc virt queue Liang Li
2016-10-27 18:29 ` Michael S. Tsirkin [this message]
2016-10-21 6:24 ` [Qemu-devel] [RESEND PATCH v3 kernel 7/7] virtio-balloon: tell host vm's unused page info Liang Li
2016-10-21 17:25 ` [Qemu-devel] [RESEND PATCH v3 kernel 0/7] Extend virtio-balloon for fast (de)inflating & fast live migration Dave Hansen
2016-10-21 19:44 ` Michael S. Tsirkin
2016-10-23 11:29 ` Li, Liang Z
2016-10-25 3:52 ` Michael S. Tsirkin
2016-10-26 10:06 ` Li, Liang Z
2016-10-26 10:13 ` Li, Liang Z
2016-10-26 18:15 ` Dave Hansen
2016-10-27 0:36 ` Li, Liang Z
2016-10-26 18:11 ` Dave Hansen
2016-10-27 0:51 ` Li, Liang Z
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=20161027211928-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=amit.shah@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dave.hansen@intel.com \
--cc=dgilbert@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=liang.z.li@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).