All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Chao Liu <lc00631@tecorigin.com>
Cc: pbonzini@redhat.com,  peterx@redhat.com,  david@redhat.com,
	philmd@linaro.org,  balaton@eik.bme.hu,  chao.liu@yeah.net,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v7 0/1] Optimizing the print format of the QEMU monitor 'info mtree'
Date: Mon, 16 Jun 2025 07:55:04 +0200	[thread overview]
Message-ID: <87frg0w7rb.fsf@pond.sub.org> (raw)
In-Reply-To: <cover.1749800810.git.chao.liu@yeah.net> (Chao Liu's message of "Fri, 13 Jun 2025 15:49:28 +0800")

Chao Liu <lc00631@tecorigin.com> writes:

> From: Chao Liu <chao.liu@yeah.net>
>
> Hi, all:
>
> After several rounds of discussion, I think that adding a -t option to the
> `info mtree` command, which enables the display of tree-like node characters
> (e.g., +--, |--), is a better approach.
>
> As BALATON Zoltan pointed out, retaining space-based indentation for displaying
> memory region (mr) nodes helps ensure that the output remains easily parseable
> by other programs. This also provides better compatibility with existing tools
> and scripts.

If people really feed the output of HMP info mtree to parsers, we should
probably provide the information via QMP.

> Users can choose between:
>
> - Without '-t': The default format using spaces for indentation, suitable for
>   scripting and parsing;
> - With '-t': The tree-style format using visual characters, ideal for
>   human-readable output.
>
> This way, both usability and compatibility are preserved.

Maintaining compatibility is a choice in HMP, not a requirement.  I'm
not judging, mind.



  parent reply	other threads:[~2025-06-16  5:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13  7:49 [PATCH v7 0/1] Optimizing the print format of the QEMU monitor 'info mtree' Chao Liu
2025-06-13  7:49 ` [PATCH v7 1/1] system: improve visual representation of node hierarchy in 'info mtree' output for qemu monitor Chao Liu
2025-06-16  5:55 ` Markus Armbruster [this message]
2025-06-16 13:45   ` [PATCH v7 0/1] Optimizing the print format of the QEMU monitor 'info mtree' Chao Liu
2025-06-16 14:44     ` Markus Armbruster
2025-06-16 15:02       ` Chao Liu
2025-06-16 16:08       ` BALATON Zoltan

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=87frg0w7rb.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=balaton@eik.bme.hu \
    --cc=chao.liu@yeah.net \
    --cc=david@redhat.com \
    --cc=lc00631@tecorigin.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --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 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.