[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAP-5=fXhPjQV-TVAYOJh7Dq72iN_H8vHsTmrtgcEtX6G2cj_6w@mail.gmail.com>
Date: Mon, 26 Jan 2026 14:07:03 -0800
From: Ian Rogers <irogers@...gle.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
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>,
Shimin Guo <shimin.guo@...dio.com>, Andi Kleen <ak@...ux.intel.com>, Leo Yan <leo.yan@....com>,
Yujie Liu <yujie.liu@...el.com>, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org
Subject: Re: [PATCH v1 0/3] perf more ELF machine usage
On Mon, Jan 26, 2026 at 1:35 PM Arnaldo Carvalho de Melo
<acme@...nel.org> wrote:
>
> On Mon, Jan 26, 2026 at 05:53:09PM -0300, Arnaldo Carvalho de Melo wrote:
> > On Mon, Jan 26, 2026 at 05:52:39PM -0300, Arnaldo Carvalho de Melo wrote:
> > > On Fri, Jan 23, 2026 at 04:16:08PM -0800, Ian Rogers wrote:
> > > > Switch 3 more cases where the perf_env arch was being used to
> > > > determine the architecture type and switch to using the ELF
> > > > machine. This includes the addition of minimal instruction parsing in
> > > > perf script for architectures other than x86, or x86 when
> > > > cross-platform.
> > > >
> > > > Note: this series will conflict with the e_flags series:
> > > > https://lore.kernel.org/lkml/20260123222209.1181249-1-irogers@google.com/
> > > > that adds an additional out argument to thread__e_machine. In all the
> > > > cases here that argument should be NULL. So:
> > > > thread__e_machine(thread, machine)
> > > > becomes:
> > > > thread__e_machine(thread, machine, /*e_flags=*/NULL)
> > >
> > > This one isn't applying.
> >
> > ⬢ [acme@...lbx perf-tools-next]$ git am ./20260123_irogers_perf_more_elf_machine_usage.mbx
> > Applying: perf script: Fix script_fetch_insn for more than just x86
> > Applying: perf callchain: Switch callchain_param_setup from an arch to an e_machine
>
> So, please try to refresh it with what is in tmp.perf-tools-next now.
>
> ⬢ [acme@...lbx perf-tools-next]$ git log --oneline -10
> 0a6fb6604746c92b (HEAD -> perf-tools-next, x1/perf-tools-next, x1/HEAD, perf-tools-next/tmp.perf-tools-next, five/perf-tools-next, five/HEAD, acme/tmp.perf-tools-next) perf session: Print all machines in session dump
> 2becdd163ab37c9d perf unwind-libdw: Wire up e_flags for CSKY
> 0403930f7b1534e3 perf perf_regs: Accurately compute register names for CSKY
> 4e66527f8859a661 perf thread: Add optional e_flags output argument to thread__e_machine
> 7d0ebeb6c0f735d4 perf dso: Factor out e_machine reading for use in thread
> 76b2cf07a6d2a836 perf vendor events amd: Fix Zen 5 MAB allocation events
> 008603bda19b2968 perf test: Fix test perf evlist for z/VM s390x
> dda5f926a1006c73 perf annotate: Fix BUILD_NONDISTRO=1 missing args->ms conversions to pointer
> 9966b382d06733f7 tools headers: Don't check arm64's unistd.h
> 129bb23a6f7d0226 Revert "perf tools: Fix arm64 build by generating unistd_64.h"
> ⬢ [acme@...lbx perf-tools-next]$
Thanks, sent now:
https://lore.kernel.org/lkml/20260126220550.2573257-1-irogers@google.com/
Ian
> - Arnaldo
Powered by blists - more mailing lists