From: Peter Xu <peterx@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>,
Mark Cave-Ayland <mark.caveayland@nutanix.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Akihiko Odaki <odaki@rsg.ci.i.u-tokyo.ac.jp>
Subject: Re: [PATCH 6/7] system/memory: Allow mtree_print_mr() to display distinct address width
Date: Wed, 4 Mar 2026 13:34:18 -0500 [thread overview]
Message-ID: <aah7KlidOr367dFO@x1.local> (raw)
In-Reply-To: <20260226220226.20164-7-philmd@linaro.org>
On Thu, Feb 26, 2026 at 11:02:24PM +0100, Philippe Mathieu-Daudé wrote:
> mtree_print_mr() display addresses using 16 chars on 64-bit
> binaries, and 8 chars on 32-bit ones. Some MR / AS don't
> always benefit of 16 chars, for example the ISA I/O region
> fits in 16 bits, and displaying 12 extra '0' in 64-bit
> binaries isn't really a good user experience.
>
> Add an extra @width argument to mtree_print_mr(). Next
> commit will make use of it.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2026-03-04 18:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 22:02 [PATCH 0/7] system/memory: Improve 'info mtree' readability Philippe Mathieu-Daudé
2026-02-26 22:02 ` [PATCH 1/7] stubs: Merge physmem.c within ram-block.c Philippe Mathieu-Daudé
2026-02-26 22:21 ` Pierrick Bouvier
2026-02-26 22:22 ` BALATON Zoltan
2026-03-02 6:21 ` Akihiko Odaki
2026-03-03 16:15 ` Philippe Mathieu-Daudé
2026-03-03 17:20 ` BALATON Zoltan
2026-03-04 6:27 ` Philippe Mathieu-Daudé
2026-03-04 11:41 ` BALATON Zoltan
2026-03-04 18:32 ` Peter Xu
2026-02-26 22:02 ` [PATCH 2/7] system/ramblock: Constify various RAMBlock arguments Philippe Mathieu-Daudé
2026-02-26 22:22 ` Pierrick Bouvier
2026-03-04 18:33 ` Peter Xu
2026-02-26 22:02 ` [PATCH 3/7] system/memory: Constify various MemoryRegion arguments Philippe Mathieu-Daudé
2026-02-26 22:22 ` Pierrick Bouvier
2026-03-04 18:33 ` Peter Xu
2026-02-26 22:02 ` [PATCH 4/7] system/memory: Have memory_region_type() correctly describe containers Philippe Mathieu-Daudé
2026-02-26 22:22 ` Pierrick Bouvier
2026-03-04 18:33 ` Peter Xu
2026-02-26 22:02 ` [PATCH 5/7] system/memory: Display address spaces starting at 0x0000.0000 Philippe Mathieu-Daudé
2026-02-26 22:23 ` Pierrick Bouvier
2026-03-04 18:24 ` Peter Xu
2026-02-26 22:02 ` [PATCH 6/7] system/memory: Allow mtree_print_mr() to display distinct address width Philippe Mathieu-Daudé
2026-02-26 22:24 ` Pierrick Bouvier
2026-03-04 18:34 ` Peter Xu [this message]
2026-02-26 22:02 ` [PATCH 7/7] system/memory: Have 'info mtree' display addresses nicely Philippe Mathieu-Daudé
2026-02-26 22:26 ` Pierrick Bouvier
2026-02-26 22:35 ` BALATON Zoltan
2026-02-27 16:20 ` Philippe Mathieu-Daudé
2026-03-04 18:35 ` 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=aah7KlidOr367dFO@x1.local \
--to=peterx@redhat.com \
--cc=mark.caveayland@nutanix.com \
--cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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.