From: Max Filippov <jcmvbkbc@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, Nicholas Piggin <npiggin@gmail.com>,
Laurent Vivier <laurent@vivier.eu>,
Anton Johansson <anjo@rev.ng>, Glenn Miles <milesg@linux.ibm.com>,
"Dr . David Alan Gilbert" <dave@treblig.org>,
qemu-ppc@nongnu.org,
Pierrick Bouvier <pierrick.bouvier@linaro.org>,
Chinmay Rath <rathc@linux.ibm.com>
Subject: Re: [PATCH-for-11.1 v2 0/7] monitor: Have 'info tlb' dump MMU information on monitor
Date: Sat, 21 Mar 2026 07:01:49 -0700 [thread overview]
Message-ID: <CAMo8BfJKapiGNtpO4zPdGiEvM9xL=4gyFyQMupDn9M8T80Hinw@mail.gmail.com> (raw)
In-Reply-To: <20260320165021.39521-1-philmd@linaro.org>
On Fri, Mar 20, 2026 at 9:50 AM Philippe Mathieu-Daudé
<philmd@linaro.org> wrote:
>
> Currently 'info tlb' dumps the MMU information on stdout, fix
That's not what I observe: I build QEMU from today's master
and run
qemu-system-xtensa -M kc705 -s -S -nographic \
-chardev socket,id=mon,host=0.0.0.0,port=7777,server=on,wait=off \
-mon chardev=mon
and `info tlb` in that monitor works as expected:
$ nc 127.0.0.1 7777
QEMU 10.2.90 monitor - type 'help' for more information
(qemu) info tlb
info tlb
ITLB:
Way 5 (128 MB)
Vaddr Paddr ASID Attr RWX Cache
---------- ---------- ---- ---- --- -------
0xd0000000 0x00000000 0x01 0x07 RWX WB
0xd8000000 0x00000000 0x01 0x03 RWX Bypass
Way 6 (256 MB)
Vaddr Paddr ASID Attr RWX Cache
---------- ---------- ---- ---- --- -------
0xe0000000 0xf0000000 0x01 0x07 RWX WB
0xf0000000 0xf0000000 0x01 0x03 RWX Bypass
DTLB:
Way 5 (128 MB)
Vaddr Paddr ASID Attr RWX Cache
---------- ---------- ---- ---- --- -------
0xd0000000 0x00000000 0x01 0x07 RWX WB
0xd8000000 0x00000000 0x01 0x03 RWX Bypass
Way 6 (256 MB)
Vaddr Paddr ASID Attr RWX Cache
---------- ---------- ---- ---- --- -------
0xe0000000 0xf0000000 0x01 0x07 RWX WB
0xf0000000 0xf0000000 0x01 0x03 RWX Bypass
> by using the monitor console instead. Rename the dump_mmu()
> functions to avoid name clash on single binary.
--
Thanks.
-- Max
prev parent reply other threads:[~2026-03-21 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 16:50 [PATCH-for-11.1 v2 0/7] monitor: Have 'info tlb' dump MMU information on monitor Philippe Mathieu-Daudé
2026-03-20 16:50 ` [PATCH-for-11.1 v2 1/7] target/m68k: " Philippe Mathieu-Daudé
2026-03-20 16:50 ` [PATCH-for-11.1 v2 2/7] target/ppc: " Philippe Mathieu-Daudé
2026-03-20 16:50 ` [PATCH-for-11.1 v2 3/7] target/xtensa: " Philippe Mathieu-Daudé
2026-03-20 18:07 ` Max Filippov
2026-03-20 16:50 ` [PATCH-for-11.1 v2 4/7] target/xtensa: Display [ID]TLB header within dump_tlb() Philippe Mathieu-Daudé
2026-03-20 18:09 ` Max Filippov
2026-03-20 16:50 ` [PATCH-for-11.1 v2 5/7] target/m68k: Rename dump_mmu() -> m68k_monitor_dump_mmu() Philippe Mathieu-Daudé
2026-03-20 16:50 ` [PATCH-for-11.1 v2 6/7] target/ppc: Rename dump_mmu() -> ppc_monitor_dump_mmu() Philippe Mathieu-Daudé
2026-03-20 16:50 ` [PATCH-for-11.1 v2 7/7] target/xtensa: Rename dump_mmu() -> xtensa_monitor_dump_mmu() Philippe Mathieu-Daudé
2026-03-20 18:10 ` Max Filippov
2026-03-21 14:01 ` Max Filippov [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='CAMo8BfJKapiGNtpO4zPdGiEvM9xL=4gyFyQMupDn9M8T80Hinw@mail.gmail.com' \
--to=jcmvbkbc@gmail.com \
--cc=anjo@rev.ng \
--cc=dave@treblig.org \
--cc=laurent@vivier.eu \
--cc=milesg@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rathc@linux.ibm.com \
/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