[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aWasKG0TD5dnpDSK@x1>
Date: Tue, 13 Jan 2026 17:33:44 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Ian Rogers <irogers@...gle.com>
Cc: James Clark <james.clark@...aro.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, Namhyung Kim <namhyung@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>, Leo Yan <leo.yan@....com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf tools: Dump callchain context marker names
On Fri, Jan 02, 2026 at 04:18:37AM -0800, Ian Rogers wrote:
> On Fri, Jan 2, 2026 at 4:16 AM James Clark <james.clark@...aro.org> wrote:
> >
> > These are hard to interpret in the raw output because they are printed
> > as hex but are defined in perf_event.h as decimal. Make it much easier
> > to read the raw callchains by just printing their names.
> >
> > For example:
> >
> > $ perf report -D
> >
> > 1798195372321 0x4638 [0xb0]: PERF_RECORD_SAMPLE(IP, 0x4002): 44922/44922: 0x7c8046dd3400 period: 120218 addr: 0
> > ... FP chain: nr:12
> > ..... 0: fffffffffffffe00 (PERF_CONTEXT_USER)
> > ..... 1: 00007c8046dd3400
> > ..... 2: 00007c8046db86d3
> >
> > Signed-off-by: James Clark <james.clark@...aro.org>
>
> Reviewed-by: Ian Rogers <irogers@...gle.com>
Thanks, applied to perf-tools-next,
- Arnaldo
Powered by blists - more mailing lists