From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
peterx@redhat.com, "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: [Qemu-devel] [PATCH v5 0/3] ramblock: add hmp command "info ramblock"
Date: Tue, 9 May 2017 19:25:02 +0800 [thread overview]
Message-ID: <1494329105-4411-1-git-send-email-peterx@redhat.com> (raw)
v5
- add r-b for Dave on first patch (which I forgot in v4, so I got it
again)
- add one more patch to introduce size_to_str() as patch 2 [Dave]
- let the last patch use the new interface
v4:
- move page_size_to_str() into util/cutil.c [Dave]
v3:
- cast the three PRIx64 addresses using (uint64_t) [Fam]
- add more comment in patch 2 to emphasize that this command is only
suitable for HMP, not QMP [Markus]
v2:
- replace "lx" with "PRIx64" in three places
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 (3):
ramblock: add RAMBLOCK_FOREACH()
utils: provide size_to_str()
ramblock: add new hmp command "info ramblock"
exec.c | 44 +++++++++++++++++++++++++++++++++-----------
hmp-commands-info.hx | 14 ++++++++++++++
hmp.c | 6 ++++++
hmp.h | 1 +
include/exec/ramlist.h | 6 ++++++
include/qemu-common.h | 1 +
migration/ram.c | 15 ++++++++-------
util/cutils.c | 26 ++++++++++++++++++++++++++
8 files changed, 95 insertions(+), 18 deletions(-)
--
2.7.4
next reply other threads:[~2017-05-09 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 11:25 Peter Xu [this message]
2017-05-09 11:25 ` [Qemu-devel] [PATCH v5 1/3] ramblock: add RAMBLOCK_FOREACH() Peter Xu
2017-05-09 11:25 ` [Qemu-devel] [PATCH v5 2/3] utils: provide size_to_str() Peter Xu
2017-05-09 14:50 ` Markus Armbruster
2017-05-10 3:32 ` Peter Xu
2017-05-09 11:25 ` [Qemu-devel] [PATCH v5 3/3] ramblock: add new hmp command "info ramblock" 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=1494329105-4411-1-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=armbru@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 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).