From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
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 v4 3/9] perf annotate: Pass annotation_print_data to annotation_line__write()
Date: Mon, 28 Jul 2025 11:44:05 -0700 [thread overview]
Message-ID: <aIfE9VWrRzPJD314@google.com> (raw)
In-Reply-To: <CAP-5=fXUyA=kgTTMDUmeOF9hURhQQxfYOFk5_HZEkQsdh7QqSg@mail.gmail.com>
On Fri, Jul 25, 2025 at 05:23:00PM -0700, Ian Rogers wrote:
> On Fri, Jul 25, 2025 at 12:38 PM Namhyung Kim <namhyung@kernel.org> wrote:
[SNIP]
> > diff --git a/tools/perf/util/annotate.h b/tools/perf/util/annotate.h
> > index 0f640e4871744262..8fad464a870a2b8e 100644
> > --- a/tools/perf/util/annotate.h
> > +++ b/tools/perf/util/annotate.h
> > @@ -199,8 +199,18 @@ struct annotation_write_ops {
> > void (*write_graph)(void *obj, int graph);
> > };
> >
> > +struct annotation_print_data {
> > + struct hist_entry *he;
> > + struct evsel *evsel;
> > + struct arch *arch;
> > + struct debuginfo *dbg;
> > + u64 start;
> > + int addr_fmt_width;
> > +};
>
> nit: As the scope of this is now global, is it worth commenting it?
> For example, where is start relative to?
Sure, I'll add comments.
>
> Reviewed-by: Ian Rogers <irogers@google.com>
Thanks,
Namhyung
next prev parent reply other threads:[~2025-07-28 18:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 19:37 [PATCHSET v4 0/9] perf annotate: Support --code-with-type on TUI Namhyung Kim
2025-07-25 19:37 ` [PATCH v4 1/9] perf annotate: Rename to __hist_entry__tui_annotate() Namhyung Kim
2025-07-26 0:16 ` Ian Rogers
2025-07-28 18:39 ` Namhyung Kim
2025-07-25 19:37 ` [PATCH v4 2/9] perf annotate: Remove __annotation_line__write() Namhyung Kim
2025-07-26 0:20 ` Ian Rogers
2025-07-28 18:42 ` Namhyung Kim
2025-07-25 19:37 ` [PATCH v4 3/9] perf annotate: Pass annotation_print_data to annotation_line__write() Namhyung Kim
2025-07-26 0:23 ` Ian Rogers
2025-07-28 18:44 ` Namhyung Kim [this message]
2025-07-25 19:37 ` [PATCH v4 4/9] perf annotate: Simplify width calculation in annotation_line__write() Namhyung Kim
2025-07-26 0:30 ` Ian Rogers
2025-07-28 18:47 ` Namhyung Kim
2025-07-25 19:37 ` [PATCH v4 5/9] perf annotate: Add --code-with-type support for TUI Namhyung Kim
2025-07-26 0:31 ` Ian Rogers
2025-07-28 18:47 ` Namhyung Kim
2025-07-25 19:37 ` [PATCH v4 6/9] perf annotate: Add 'T' hot key to toggle data type display Namhyung Kim
2025-07-26 0:34 ` Ian Rogers
2025-07-25 19:37 ` [PATCH v4 7/9] perf annotate: Show warning when debuginfo is not available Namhyung Kim
2025-07-26 0:38 ` Ian Rogers
2025-07-25 19:37 ` [PATCH v4 8/9] perf annotate: Hide data-type for stack operation and canary Namhyung Kim
2025-07-26 0:44 ` Ian Rogers
2025-07-28 18:51 ` Namhyung Kim
2025-07-25 19:37 ` [PATCH v4 9/9] perf annotate: Add dso__debuginfo() helper Namhyung Kim
2025-07-26 0:46 ` Ian Rogers
2025-07-28 18:54 ` 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=aIfE9VWrRzPJD314@google.com \
--to=namhyung@kernel.org \
--cc=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=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.