From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, marcandre.lureau@gmail.com,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
peterx@redhat.com
Subject: [Qemu-devel] [PATCH v4 0/2] memory: extend "info mtree" with flat view dump
Date: Mon, 16 Jan 2017 16:40:03 +0800 [thread overview]
Message-ID: <1484556005-29701-1-git-send-email-peterx@redhat.com> (raw)
v4:
- do unref of flatview when no view is there [Dave]
v3:
- rather than dump flatview directly in "info mtree", provide a new
parameter "-f" for it. [Paolo]
- replace "RW" chars with the type of memory region [Paolo]
- (cc dave as well since it touches HMP interface)
v2:
- fix a size error in patch 2
- add r-b for Marc-André in patch 1
Each address space has its own flatview. It's another way to observe
memory info besides the default memory region hierachy, for example,
if we want to know which memory region will handle the write to
specific address, a flatview will suite more here than the default
hierachical dump.
Please review. Thanks,
Peter Xu (2):
memory: tune mtree_print_mr() to dump mr type
memory: hmp: add "-f" for "info mtree"
hmp-commands-info.hx | 6 ++--
include/exec/memory.h | 2 +-
memory.c | 89 ++++++++++++++++++++++++++++++++++++++-------------
monitor.c | 4 ++-
4 files changed, 74 insertions(+), 27 deletions(-)
--
2.7.4
next reply other threads:[~2017-01-16 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 8:40 Peter Xu [this message]
2017-01-16 8:40 ` [Qemu-devel] [PATCH v4 1/2] memory: tune mtree_print_mr() to dump mr type Peter Xu
2017-01-17 19:23 ` Dr. David Alan Gilbert
2017-01-16 8:40 ` [Qemu-devel] [PATCH v4 2/2] memory: hmp: add "-f" for "info mtree" Peter Xu
2017-01-17 17:37 ` Dr. David Alan Gilbert
2017-01-18 9:05 ` [Qemu-devel] [PATCH v4 0/2] memory: extend "info mtree" with flat view dump Paolo Bonzini
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=1484556005-29701-1-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=marcandre.lureau@gmail.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.