From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: marcandre.lureau@gmail.com
Subject: Re: [Qemu-devel] [PATCH v2 2/2] memory: hmp: dump flat view for 'info mtree'
Date: Wed, 11 Jan 2017 18:13:11 +0100 [thread overview]
Message-ID: <9c2b7dcd-c3dd-054a-cf4f-2eaaec084cf4@redhat.com> (raw)
In-Reply-To: <1482307137-5106-3-git-send-email-peterx@redhat.com>
On 21/12/2016 08:58, Peter Xu wrote:
> Dumping flat view will be useful to debug the memory rendering logic,
> also it'll be much easier with it to know what memory region is handling
> what address range.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
This is useful, but dumping both makes the output very long. What about
adding a -f option to "info mtree"?
Paolo
> ---
> memory.c | 31 +++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/memory.c b/memory.c
> index 5dcc2e1..91341d3 100644
> --- a/memory.c
> +++ b/memory.c
> @@ -2545,6 +2545,36 @@ static void mtree_print_mr(fprintf_function mon_printf, void *f,
> }
> }
>
> +static void mtree_print_flatview(fprintf_function p, void *f,
> + AddressSpace *as)
> +{
> + FlatView *view = address_space_get_flatview(as);
> + FlatRange *range = &view->ranges[0];
> + MemoryRegion *mr;
> + int n = view->nr;
> +
> + if (n <= 0) {
> + p(f, MTREE_INDENT "No rendered FlatView for "
> + "address space '%s'\n", as->name);
> + return;
> + }
> +
> + p(f, MTREE_INDENT "FlatView (address space '%s'):\n", as->name);
> +
> + while (n--) {
> + mr = range->mr;
> + p(f, MTREE_INDENT MTREE_INDENT TARGET_FMT_plx "-"
> + TARGET_FMT_plx " (prio %d, %c%c): %s\n",
> + int128_get64(range->addr.start),
> + int128_get64(range->addr.start) + MR_SIZE(range->addr.size),
> + mr->priority, MR_CHAR_RD(mr), MR_CHAR_WR(mr),
> + memory_region_name(mr));
> + range++;
> + }
> +
> + flatview_unref(view);
> +}
> +
> void mtree_info(fprintf_function mon_printf, void *f)
> {
> MemoryRegionListHead ml_head;
> @@ -2556,6 +2586,7 @@ void mtree_info(fprintf_function mon_printf, void *f)
> QTAILQ_FOREACH(as, &address_spaces, address_spaces_link) {
> mon_printf(f, "address-space: %s\n", as->name);
> mtree_print_mr(mon_printf, f, as->root, 1, 0, &ml_head);
> + mtree_print_flatview(mon_printf, f, as);
> mon_printf(f, "\n");
> }
>
>
next prev parent reply other threads:[~2017-01-11 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 7:58 [Qemu-devel] [PATCH v2 0/2] memory: extend "info mtree" with flat view dump Peter Xu
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 [this message]
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=9c2b7dcd-c3dd-054a-cf4f-2eaaec084cf4@redhat.com \
--to=pbonzini@redhat.com \
--cc=marcandre.lureau@gmail.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).