From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, marcandre.lureau@gmail.com, peterx@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] memory: extend "info mtree" with flat view dump
Date: Wed, 21 Dec 2016 15:58:55 +0800 [thread overview]
Message-ID: <1482307137-5106-1-git-send-email-peterx@redhat.com> (raw)
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.
I used it to debug a vt-d memory region overlap issue. Do we need
this? I think we can at least consider patch 1, which is a cleanup of
existing codes. :)
Please review. Thanks,
Peter Xu (2):
memory: provide common macros for mtree_print_mr()
memory: hmp: dump flat view for 'info mtree'
memory.c | 65 +++++++++++++++++++++++++++++++++++++++++++++-------------------
1 file changed, 46 insertions(+), 19 deletions(-)
--
2.7.4
next reply other threads:[~2016-12-21 7:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 7:58 Peter Xu [this message]
2016-12-21 7:58 ` [Qemu-devel] [PATCH v2 1/2] memory: provide common macros for mtree_print_mr() Peter Xu
2017-01-11 17:21 ` Paolo Bonzini
2017-01-12 5:50 ` Peter Xu
2017-01-12 8:54 ` Paolo Bonzini
2017-01-12 9:46 ` Peter Xu
2017-01-12 11:19 ` Paolo Bonzini
2017-01-12 13:09 ` Peter Xu
2016-12-21 7:58 ` [Qemu-devel] [PATCH v2 2/2] memory: hmp: dump flat view for 'info mtree' Peter Xu
2017-01-11 17:13 ` Paolo Bonzini
2017-01-12 5:53 ` Peter Xu
2017-01-11 6:20 ` [Qemu-devel] [PATCH v2 0/2] memory: extend "info mtree" with flat view dump 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=1482307137-5106-1-git-send-email-peterx@redhat.com \
--to=peterx@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 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).