linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCHSET v5 00/12] perf annotate: Support --code-with-type on TUI
Date: Wed, 20 Aug 2025 18:43:03 -0300	[thread overview]
Message-ID: <aKZBZ2I04-p_Yl_m@x1> (raw)
In-Reply-To: <aKZA5bE1ibDMJpuw@x1>

On Wed, Aug 20, 2025 at 06:40:53PM -0300, Arnaldo Carvalho de Melo wrote:
> On Fri, Aug 15, 2025 at 08:16:23PM -0700, Namhyung Kim wrote:
> > 
> > Hello,
> > 
> > The --code-with-type option is to show normal annotate output with type
> > information.  It was supported only on --stdio, but this change adds it
> > to TUI as well.
> > 
> > Arnaldo, please tell me if you still don't like the
> > __hist_entry__tui_annotate() but I don't have a better idea for now.
> 
> Not a problem, I tested everything, all seems to work as advertised.
> 
> The minor suggestions I made I can do while merging, if you don't mind
> and agree with them.

I mean the scope of a variable, a missing line before an if line, not
the other more involved one as the alignment of the type comments, etc.
:-)

- Arnaldo
 
> Please let me know.
> 
> Tested-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> 
> - Arnaldo
>  
> > v5 changes)
> >  * use a copy of hist entry for perf top  (Ian)
> >  * split disasm_line__write() change  (Ian)
> >  * constify annotation_write_ops parameter  (Ian)
> >  * update printed length calculation  (Ian)
> >  * remove annotation_print_data.start
> >  * add a hashmap to skip duplicate processing
> > 
> > v4 changes)
> >  * add dso__debuginfo() helper  (Ian)
> > 
> > v3 changes)
> >  * hide stack operation and stack canary by default
> > 
> > v2 changes)
> >  * use 'T' key to toggle data type display  (Arnaldo)
> >  * display '[Type]' in the title line when it's enabled  (Arnaldo)
> >  * show warning when debug info is not available  (Arnaldo)
> >  * fix a typo  (Arnaldo)
> > 
> > Actually the command line option sets the default behavior and users can
> > change it by pressing 'T' key in the TUI annotate browser.
> > 
> > The code is also available at 'perf/annotate-code-type-tui-v5' branch at
> > https://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
> > 
> > Thanks,
> > Namhyung
> > 
> > 
> > Namhyung Kim (12):
> >   perf annotate: Rename to __hist_entry__tui_annotate()
> >   perf annotate: Remove annotation_print_data.start
> >   perf annotate: Remove __annotation_line__write()
> >   perf annotate: Pass annotation_print_data to annotation_line__write()
> >   perf annotate: Simplify width calculation in annotation_line__write()
> >   perf annotate: Return printed number from disasm_line__write()
> >   perf annotate: Add --code-with-type support for TUI
> >   perf annotate: Add 'T' hot key to toggle data type display
> >   perf annotate: Show warning when debuginfo is not available
> >   perf annotate: Hide data-type for stack operation and canary
> >   perf annotate: Add dso__debuginfo() helper
> >   perf annotate: Use a hashmap to save type data
> > 
> >  tools/perf/Documentation/perf-annotate.txt |   1 -
> >  tools/perf/builtin-annotate.c              |   5 -
> >  tools/perf/ui/browsers/annotate.c          | 117 ++++++++++++--
> >  tools/perf/ui/browsers/hists.c             |   2 +-
> >  tools/perf/util/annotate.c                 | 178 +++++++++++++++------
> >  tools/perf/util/annotate.h                 |  29 ++--
> >  tools/perf/util/dso.h                      |  21 +++
> >  tools/perf/util/hist.h                     |  12 +-
> >  8 files changed, 273 insertions(+), 92 deletions(-)
> > 
> > -- 
> > 2.50.1

  reply	other threads:[~2025-08-20 21:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16  3:16 [PATCHSET v5 00/12] perf annotate: Support --code-with-type on TUI Namhyung Kim
2025-08-16  3:16 ` [PATCH v5 01/12] perf annotate: Rename to __hist_entry__tui_annotate() Namhyung Kim
2025-08-16  3:16 ` [PATCH v5 02/12] perf annotate: Remove annotation_print_data.start Namhyung Kim
2025-08-16  3:16 ` [PATCH v5 03/12] perf annotate: Remove __annotation_line__write() Namhyung Kim
2025-08-16  3:16 ` [PATCH v5 04/12] perf annotate: Pass annotation_print_data to annotation_line__write() Namhyung Kim
2025-08-16  3:16 ` [PATCH v5 05/12] perf annotate: Simplify width calculation in annotation_line__write() Namhyung Kim
2025-08-16  3:16 ` [PATCH v5 06/12] perf annotate: Return printed number from disasm_line__write() Namhyung Kim
2025-08-16  3:16 ` [PATCH v5 07/12] perf annotate: Add --code-with-type support for TUI Namhyung Kim
2025-08-20 18:54   ` Arnaldo Carvalho de Melo
2025-08-20 23:38     ` Namhyung Kim
2025-08-16  3:16 ` [PATCH v5 08/12] perf annotate: Add 'T' hot key to toggle data type display Namhyung Kim
2025-08-20 21:13   ` Arnaldo Carvalho de Melo
2025-08-20 23:43     ` Namhyung Kim
2025-08-16  3:16 ` [PATCH v5 09/12] perf annotate: Show warning when debuginfo is not available Namhyung Kim
2025-08-16  3:16 ` [PATCH v5 10/12] perf annotate: Hide data-type for stack operation and canary Namhyung Kim
2025-08-20 21:28   ` Arnaldo Carvalho de Melo
2025-08-20 21:30     ` Arnaldo Carvalho de Melo
2025-08-16  3:16 ` [PATCH v5 11/12] perf annotate: Add dso__debuginfo() helper Namhyung Kim
2025-08-16  3:16 ` [PATCH v5 12/12] perf annotate: Use a hashmap to save type data Namhyung Kim
2025-08-20 21:37   ` Arnaldo Carvalho de Melo
2025-08-20 23:46     ` Namhyung Kim
2025-08-20 21:40 ` [PATCHSET v5 00/12] perf annotate: Support --code-with-type on TUI Arnaldo Carvalho de Melo
2025-08-20 21:43   ` Arnaldo Carvalho de Melo [this message]
2025-08-20 23:47     ` Namhyung Kim

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=aKZBZ2I04-p_Yl_m@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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).