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 v5 10/12] perf annotate: Hide data-type for stack operation and canary
Date: Wed, 20 Aug 2025 18:30:29 -0300 [thread overview]
Message-ID: <aKY-deTOzHz6n0ZQ@x1> (raw)
In-Reply-To: <aKY-Ed1ZjOgRi8As@x1>
On Wed, Aug 20, 2025 at 06:28:53PM -0300, Arnaldo Carvalho de Melo wrote:
> On Fri, Aug 15, 2025 at 08:16:33PM -0700, Namhyung Kim wrote:
> > It's mostly unnecessary to print when it has no actual type information
> > like in the stack operations and canary. Let's have them if -v option
> > is given.
>
> In the main 'report' TUI the 'V' key is wired to bumping the verbose
> level, wiring it up in the annotation view seems in order :-)
So using just 'perf top', then pressing 'V' and then going into the
annotation gets the verbose level needed to show these stack operations
in the annotate view :-)
- Arnaldo
> > Before:
> > $ perf annotate --code-with-type
> > ...
> > : 0 0xd640 <_dl_relocate_object>:
> > 0.00 : 0: endbr64
> > 0.00 : 4: pushq %rbp # data-type: (stack operation)
> > 0.00 : 5: movq %rsp, %rbp
> > 0.00 : 8: pushq %r15 # data-type: (stack operation)
> > 0.00 : a: pushq %r14 # data-type: (stack operation)
> > 0.00 : c: pushq %r13 # data-type: (stack operation)
> > 0.00 : e: pushq %r12 # data-type: (stack operation)
> > 0.00 : 10: pushq %rbx # data-type: (stack operation)
> > 0.00 : 11: subq $0xf8, %rsp
> > ...
> > 0.00 : d4: testl %eax, %eax
> > 0.00 : d6: jne 0xf424
> > 0.00 : dc: movq 0xf0(%r14), %rbx # data-type: struct link_map +0xf0
> > 0.00 : e3: testq %rbx, %rbx
> > 0.00 : e6: jne 0xf2dd
> > 0.00 : ec: cmpq $0, 0xf8(%r14) # data-type: struct link_map +0xf8
> > ...
> >
> > After:
> > : 0 0xd640 <_dl_relocate_object>:
> > 0.00 : 0: endbr64
> > 0.00 : 4: pushq %rbp
> > 0.00 : 5: movq %rsp, %rbp
> > 0.00 : 8: pushq %r15
> > 0.00 : a: pushq %r14
> > 0.00 : c: pushq %r13
> > 0.00 : e: pushq %r12
> > 0.00 : 10: pushq %rbx
> > 0.00 : 11: subq $0xf8, %rsp
> > ...
> > 0.00 : d4: testl %eax, %eax
> > 0.00 : d6: jne 0xf424
> > 0.00 : dc: movq 0xf0(%r14), %rbx # data-type: struct link_map +0xf0
> > 0.00 : e3: testq %rbx, %rbx
> > 0.00 : e6: jne 0xf2dd
> > 0.00 : ec: cmpq $0, 0xf8(%r14) # data-type: struct link_map +0xf8
> > ...
> >
> > Reviewed-by: Ian Rogers <irogers@google.com>
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> > ---
> > tools/perf/util/annotate.c | 15 +++++++++++++--
> > 1 file changed, 13 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/perf/util/annotate.c b/tools/perf/util/annotate.c
> > index 99e976d254493de2..ea68b32da7ce584a 100644
> > --- a/tools/perf/util/annotate.c
> > +++ b/tools/perf/util/annotate.c
> > @@ -765,6 +765,17 @@ __hist_entry__get_data_type(struct hist_entry *he, struct arch *arch,
> > struct debuginfo *dbg, struct disasm_line *dl,
> > int *type_offset);
> >
> > +static bool needs_type_info(struct annotated_data_type *data_type)
> > +{
> > + if (data_type == NULL || data_type == NO_TYPE)
> > + return false;
> > +
> > + if (verbose)
> > + return true;
> > +
> > + return (data_type != &stackop_type) && (data_type != &canary_type);
> > +}
> > +
> > static int
> > annotation_line__print(struct annotation_line *al, struct annotation_print_data *apd,
> > struct annotation_options *opts, int printed,
> > @@ -844,7 +855,7 @@ annotation_line__print(struct annotation_line *al, struct annotation_print_data
> >
> > data_type = __hist_entry__get_data_type(apd->he, apd->arch,
> > apd->dbg, dl, &offset);
> > - if (data_type && data_type != NO_TYPE) {
> > + if (needs_type_info(data_type)) {
> > char buf[4096];
> >
> > printf("\t\t# data-type: %s",
> > @@ -1958,7 +1969,7 @@ static int disasm_line__snprint_type_info(struct disasm_line *dl,
> > return 1;
> >
> > data_type = __hist_entry__get_data_type(apd->he, apd->arch, apd->dbg, dl, &offset);
> > - if (data_type == NULL || data_type == NO_TYPE)
> > + if (!needs_type_info(data_type))
> > return 1;
> >
> > printed = scnprintf(buf, len, "\t\t# data-type: %s", data_type->self.type_name);
> > --
> > 2.50.1
> >
next prev parent reply other threads:[~2025-08-20 21:30 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 [this message]
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
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=aKY-deTOzHz6n0ZQ@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 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.