All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	peterx@redhat.com, "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] ramblock: add hmp command "info ramblock"
Date: Wed, 26 Apr 2017 15:44:33 +0800	[thread overview]
Message-ID: <1493192675-16104-1-git-send-email-peterx@redhat.com> (raw)

Sometimes I would like to know ramblock info for a VM. This command
would help. It provides a way to dump ramblock info. Currently the
list is by default sorted by size, though I think it's good enough.

Please review, thanks.

Peter Xu (2):
  ramblock: add RAMBLOCK_FOREACH()
  ramblock: add new hmp command "info ramblock"

 exec.c                 | 56 ++++++++++++++++++++++++++++++++++++++++----------
 hmp-commands-info.hx   | 14 +++++++++++++
 hmp.c                  |  6 ++++++
 hmp.h                  |  1 +
 include/exec/ramlist.h |  6 ++++++
 migration/ram.c        | 15 +++++++-------
 6 files changed, 80 insertions(+), 18 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-04-26  7:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26  7:44 Peter Xu [this message]
2017-04-26  7:44 ` [Qemu-devel] [PATCH 1/2] ramblock: add RAMBLOCK_FOREACH() Peter Xu
2017-04-26  7:44 ` [Qemu-devel] [PATCH 2/2] ramblock: add new hmp command "info ramblock" Peter Xu
2017-04-26 12:10   ` Markus Armbruster
2017-04-27  2:09     ` Peter Xu
2017-04-27  7:07       ` Markus Armbruster
2017-04-27  7:39         ` Paolo Bonzini
2017-04-27  7:57           ` Markus Armbruster
2017-04-27  8:06             ` Peter Xu
2017-04-26 10:21 ` [Qemu-devel] [PATCH 0/2] ramblock: add " no-reply
2017-04-26 10:32   ` Peter Xu

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=1493192675-16104-1-git-send-email-peterx@redhat.com \
    --to=peterx@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 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.