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: [PATCH v3 5/8] perf annotate: Add --code-with-type support for TUI
Date: Wed, 23 Jul 2025 13:20:27 -0300	[thread overview]
Message-ID: <aIELyy7jg5gSlkVT@x1> (raw)
In-Reply-To: <aIEH99tRH8EoqBA5@x1>

On Wed, Jul 23, 2025 at 01:04:11PM -0300, Arnaldo Carvalho de Melo wrote:
> On Tue, Jul 15, 2025 at 10:00:51PM -0700, Namhyung Kim wrote:
> > Until now, the --code-with-type option is available only on stdio.
> > But it was an artifical limitation because of an implemention issue.
> > 
> > Implement the same logic in annotation_line__write() for stdio2/TUI.
> > Make disasm_line__write() return the number of printed characters so
> > that it can skip unnecessary operations when the screen is full.
> > 
> > Remove the limitation and update the man page.
> > 
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > ---
> >  tools/perf/Documentation/perf-annotate.txt |  1 -
> >  tools/perf/builtin-annotate.c              |  5 --
> >  tools/perf/ui/browsers/annotate.c          |  6 +++
> >  tools/perf/util/annotate.c                 | 61 +++++++++++++++++++---
> >  4 files changed, 61 insertions(+), 12 deletions(-)
> > 
> > diff --git a/tools/perf/Documentation/perf-annotate.txt b/tools/perf/Documentation/perf-annotate.txt
> > index 46090c5b42b4762f..547f1a2680185e3c 100644
> > --- a/tools/perf/Documentation/perf-annotate.txt
> > +++ b/tools/perf/Documentation/perf-annotate.txt
> > @@ -170,7 +170,6 @@ include::itrace.txt[]
> >  
> >  --code-with-type::
> >  	Show data type info in code annotation (for memory instructions only).
> > -	Currently it only works with --stdio option.
> >  
> >  
> >  SEE ALSO
> > diff --git a/tools/perf/builtin-annotate.c b/tools/perf/builtin-annotate.c
> > index 9833c2c82a2fee46..6debd725392db4a4 100644
> > --- a/tools/perf/builtin-annotate.c
> > +++ b/tools/perf/builtin-annotate.c
> > @@ -917,11 +917,6 @@ int cmd_annotate(int argc, const char **argv)
> >  		symbol_conf.annotate_data_sample = true;
> >  	} else if (annotate_opts.code_with_type) {
> >  		symbol_conf.annotate_data_member = true;
> > -
> > -		if (!annotate.use_stdio) {
> > -			pr_err("--code-with-type only works with --stdio.\n");
> > -			goto out_delete;
> > -		}
> >  	}
> >  
> >  	setup_browser(true);
> > diff --git a/tools/perf/ui/browsers/annotate.c b/tools/perf/ui/browsers/annotate.c
> > index 23bea5b165774ae7..cdee1969f3131a7c 100644
> > --- a/tools/perf/ui/browsers/annotate.c
> > +++ b/tools/perf/ui/browsers/annotate.c
> > @@ -4,6 +4,7 @@
> >  #include "../ui.h"
> >  #include "../../util/annotate.h"
> >  #include "../../util/debug.h"
> > +#include "../../util/debuginfo.h"
> >  #include "../../util/dso.h"
> >  #include "../../util/hist.h"
> >  #include "../../util/sort.h"
> > @@ -1101,6 +1102,9 @@ int __hist_entry__tui_annotate(struct hist_entry *he, struct map_symbol *ms,
> >  
> >  	ui_helpline__push("Press ESC to exit");
> >  
> > +	if (annotate_opts.code_with_type)
> > +		browser.dbg = debuginfo__new(dso__long_name(dso));
> 
> Some error checking here to tell the user if debuginfo isn't available
> and hints on how to get it in place?

Ok, you did it  later with:

commit 81d638a1b96ec04d7c41e163b5077419cf85e798 (HEAD)
Author: Namhyung Kim <namhyung@kernel.org>
Date:   Tue Jul 15 22:00:53 2025 -0700

    perf annotate: Show warning when debuginfo is not available
    
    When user requests data-type annotation but no DWARF info is available,
    show a warning message about it.

- Arnaldo

  reply	other threads:[~2025-07-23 16:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16  5:00 [PATCHSET v3 0/8] perf annotate: Support --code-with-type on TUI Namhyung Kim
2025-07-16  5:00 ` [PATCH v3 1/8] perf annotate: Rename to __hist_entry__tui_annotate() Namhyung Kim
2025-07-16 20:16   ` Arnaldo Carvalho de Melo
2025-07-17  0:55     ` Namhyung Kim
2025-07-16  5:00 ` [PATCH v3 2/8] perf annotate: Remove __annotation_line__write() Namhyung Kim
2025-07-16  5:00 ` [PATCH v3 3/8] perf annotate: Pass annotation_print_data to annotation_line__write() Namhyung Kim
2025-07-16  5:00 ` [PATCH v3 4/8] perf annotate: Simplify width calculation in annotation_line__write() Namhyung Kim
2025-07-16  5:00 ` [PATCH v3 5/8] perf annotate: Add --code-with-type support for TUI Namhyung Kim
2025-07-16 15:00   ` Ian Rogers
2025-07-16 17:27     ` Namhyung Kim
2025-07-16 20:42       ` Ian Rogers
2025-07-23 16:10         ` Arnaldo Carvalho de Melo
2025-07-25 18:28         ` Namhyung Kim
2025-07-23 16:04   ` Arnaldo Carvalho de Melo
2025-07-23 16:20     ` Arnaldo Carvalho de Melo [this message]
2025-07-16  5:00 ` [PATCH v3 6/8] perf annotate: Add 'T' hot key to toggle data type display Namhyung Kim
2025-07-16  5:00 ` [PATCH v3 7/8] perf annotate: Show warning when debuginfo is not available Namhyung Kim
2025-07-16  5:00 ` [PATCH v3 8/8] perf annotate: Hide data-type for stack operation and canary Namhyung Kim
2025-07-16 15:02 ` [PATCHSET v3 0/8] perf annotate: Support --code-with-type on TUI Ian Rogers

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=aIELyy7jg5gSlkVT@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).