From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Eric Blake <eblake@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v8 0/3] ramblock: add hmp command "info ramblock"
Date: Wed, 17 May 2017 17:31:47 +0100 [thread overview]
Message-ID: <20170517163146.GD2444@work-vm> (raw)
In-Reply-To: <1494562661-9063-1-git-send-email-peterx@redhat.com>
* Peter Xu (peterx@redhat.com) wrote:
> v8:
Queued for HMP
> - patch 1: add r-b for Dave
> - patch 2: use "uint64_t" for size_to_str() parameter, remove assert()
> since it's useless now [Dave]
> - drop patch 4
>
> v7:
> - patch 1: removed Dave's r-b since the patch conflicted during rebase
> - patch 2: add r-b for Markus, with the nice function comment that
> provided [Markus]
> - patch 3: add r-b for Dave
> - patch 4 (new): added new patch to remove assert in size_to_str(),
> assuming that would be better.
>
> v6
> - patch 2: instead of create a new size_to_str(), abstract the logic
> out from print_type_size(), refactor it, to make sure
> print_type_size() dumps exactly the same thing as before. (a simple
> test with info qtree is done)
> - let suffixes be an array of strings [Markus]
>
> 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 | 13 +++++++------
> qapi/string-output-visitor.c | 22 ++++++----------------
> util/cutils.c | 25 +++++++++++++++++++++++++
> 9 files changed, 99 insertions(+), 33 deletions(-)
>
> --
> 2.7.4
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2017-05-17 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 4:17 [Qemu-devel] [PATCH v8 0/3] ramblock: add hmp command "info ramblock" Peter Xu
2017-05-12 4:17 ` [Qemu-devel] [PATCH v8 1/3] ramblock: add RAMBLOCK_FOREACH() Peter Xu
2017-05-12 4:17 ` [Qemu-devel] [PATCH v8 2/3] utils: provide size_to_str() Peter Xu
2017-05-12 9:42 ` Dr. David Alan Gilbert
2017-05-16 16:34 ` Markus Armbruster
2017-05-12 4:17 ` [Qemu-devel] [PATCH v8 3/3] ramblock: add new hmp command "info ramblock" Peter Xu
2017-05-17 16:31 ` Dr. David Alan Gilbert [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=20170517163146.GD2444@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@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).