[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aXfT5XlRkURVMwDB@x1>
Date: Mon, 26 Jan 2026 17:51:49 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Ian Rogers <irogers@...gle.com>
Cc: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
James Clark <james.clark@...aro.org>, Guo Ren <guoren@...nel.org>,
Tianyou Li <tianyou.li@...el.com>,
Athira Rajeev <atrajeev@...ux.ibm.com>,
Stephen Brennan <stephen.s.brennan@...cle.com>,
Aditya Bodkhe <aditya.b1@...ux.ibm.com>,
Chun-Tse Shao <ctshao@...gle.com>,
Swapnil Sapkal <swapnil.sapkal@....com>,
Howard Chu <howardchu95@...il.com>,
Sergei Trofimovich <slyich@...il.com>,
Shimin Guo <shimin.guo@...dio.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-csky@...r.kernel.org
Subject: Re: [PATCH v1 0/4] perf e_flags support for CSKY
On Fri, Jan 23, 2026 at 02:22:05PM -0800, Ian Rogers wrote:
> The ELF machine type for CSKY is insufficent to describe the perf
> registers, the e_flags from the ELF header is also required. Expand
> the thread__e_machine and associated APIs to optionally fill in an
> e_flags output field. For uses in `perf trace` the e_flags doesn't
> matter and the e_flags needn't be computed. For `perf annotate` the
> e_flags are computed and passed around, however, this is optimized so
> the e_flags are only read for EM_CSKY. Call chain unwinding needs to
> know about perf registers during recording and in the unwinding logic,
> this is similarly wired up with the e_flags.
>
> Ian Rogers (4):
> perf dso: Factor out e_machine reading for use in thread
> perf thread: Add optional e_flags output argument to thread__e_machine
> perf perf_regs: Accurately compute register names for CSKY
> perf unwind-libdw: Wire up e_flags for CSKY
Thanks, applied to perf-tools-next,
- Arnaldo
Powered by blists - more mailing lists