All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
To: "Dr. David Alan Gilbert" <dave@treblig.org>,
	"Marc-André Lureau" <marcandre.lureau@gmail.com>,
	armbru@redhat.com
Cc: AlanoSong@163.com, qemu-devel@nongnu.org, laurent@vivier.eu,
	zhao1.liu@intel.com, atar4qemu@gmail.com
Subject: Re: [PATCH v3] monitor: Refine 'info tlb' command
Date: Fri, 4 Sep 2026 13:11:21 +0200	[thread overview]
Message-ID: <dff55838-6fd4-4345-8a04-dd62f46e317c@oss.qualcomm.com> (raw)
In-Reply-To: <apncP_5e7fcofZL8@gallifrey>

On 3/9/26 22:44, Dr. David Alan Gilbert wrote:
> Hi Markus,
> 
> * Dr. David Alan Gilbert (dave@treblig.org) wrote:
>> * Marc-André Lureau (marcandre.lureau@gmail.com) wrote:
>>> Hi
>>>
>>> On Tue, Aug 18, 2026 at 5:30 PM <AlanoSong@163.com> wrote:
>>>>
>>>> When booting an i386 target, the 'info tlb' command
>>>> may walk the entire page table hierarchy and emit
>>>> an enormous amount of output. It will take dozens of
>>>> minutes to print all the info, and
>>>> The same situation also occurred on sparc32 and
>>>> m68k targets.
>>>>
>>>> So this change do the following:
>>>> 1) Add a address range argument to help user control
>>>>     the number of output items.
>>>> 2) Add warning note in help message that such address
>>>>     range argument only supported on target i386,
>>>>     sparc32 and m68k.
>>>> 3) Print ignore warning when user add such address
>>>>     range argument on other targets (sh4, sparc64,
>>>>     ppc and xtensa). Those targets only print limited
>>>>     tlb info.
>>>>
>>>> Signed-off-by: Alano Song <AlanoSong@163.com>
>>>
>>> lgtm overall
>>>
>>> - m68k print_address_zone() used to be called with page-aligned zones,
>>> but now it is clipped to arbitrary user ranges, which may not be
>>> aligned. 1 byte range will be reported as 0kb. We may want to handle
>>> the case for small ranges. Btw that code could use the macros KiB for
>>> readability
>>>
>>> - A later patch could prune non-overlapping ranges during traversal,
>>> not just during printing
>>
>> Yeh I'd say it's OK, two thoughts:
>>    a) I'd have split the patch into a series with more managable chunks
>>    b) There's quite a bit of repetition which feels like a common helper
>>     might have removed.
>>
>> But:
>>
>> Reviewed-by: Dr. David Alan Gilbert <dave@treblig.org>
> 
> Can you pick this one up please?

Doesn't this series need a rebase on top of commit
93b9a2436564a9df25a0b978c8245fed255264f2 (Make HMP optional)?

> 
> Dave
> 
>> Dave
>>
>>>> ---
>>>>   hmp-commands-info.hx      | 17 ++++++--
>>>>   target/i386/monitor.c     | 92 ++++++++++++++++++++++++++++-----------
>>>>   target/m68k/cpu.h         |  2 +-
>>>>   target/m68k/helper.c      | 55 +++++++++++++++--------
>>>>   target/m68k/monitor.c     | 15 ++++++-
>>>>   target/ppc/monitor.c      |  6 +++
>>>>   target/sh4/monitor.c      |  5 +++
>>>>   target/sparc/cpu.h        |  3 ++
>>>>   target/sparc/mmu_helper.c | 40 +++++++++++++----
>>>>   target/sparc/monitor.c    | 23 ++++++++++
>>>>   target/xtensa/monitor.c   |  6 +++
>>>>   11 files changed, 206 insertions(+), 58 deletions(-)



  reply	other threads:[~2026-09-04 11:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18 13:25 [PATCH v3] monitor: Refine 'info tlb' command AlanoSong
2026-08-18 13:36 ` Philippe Mathieu-Daudé
2026-08-18 15:12 ` Marc-André Lureau
2026-08-18 23:08   ` Dr. David Alan Gilbert
2026-09-03 20:44     ` Dr. David Alan Gilbert
2026-09-04 11:11       ` Philippe Mathieu-Daudé [this message]
2026-09-04 11:29         ` Markus Armbruster

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=dff55838-6fd4-4345-8a04-dd62f46e317c@oss.qualcomm.com \
    --to=philmd@oss.qualcomm.com \
    --cc=AlanoSong@163.com \
    --cc=armbru@redhat.com \
    --cc=atar4qemu@gmail.com \
    --cc=dave@treblig.org \
    --cc=laurent@vivier.eu \
    --cc=marcandre.lureau@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhao1.liu@intel.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 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.