public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	Shimin Guo <shimin.guo@skydio.com>,
	Andi Kleen <ak@linux.intel.com>, Leo Yan <leo.yan@arm.com>,
	Yujie Liu <yujie.liu@intel.com>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1 0/3] perf more ELF machine usage
Date: Mon, 26 Jan 2026 18:35:49 -0300	[thread overview]
Message-ID: <aXfeNfYgDVXhkrKM@x1> (raw)
In-Reply-To: <aXfUNewGdbqqQL18@x1>

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@toolbx 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@toolbx 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@toolbx perf-tools-next]$

- Arnaldo

  reply	other threads:[~2026-01-26 21:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-24  0:16 [PATCH v1 0/3] perf more ELF machine usage Ian Rogers
2026-01-24  0:16 ` [PATCH v1 1/3] perf script: Fix script_fetch_insn for more than just x86 Ian Rogers
2026-01-24  0:16 ` [PATCH v1 2/3] perf callchain: Switch callchain_param_setup from an arch to an e_machine Ian Rogers
2026-01-24  0:16 ` [PATCH v1 3/3] perf thread-stack: Switch thread_stack__init to use e_machine Ian Rogers
2026-01-26 20:52 ` [PATCH v1 0/3] perf more ELF machine usage Arnaldo Carvalho de Melo
2026-01-26 20:53   ` Arnaldo Carvalho de Melo
2026-01-26 21:35     ` Arnaldo Carvalho de Melo [this message]
2026-01-26 22:07       ` Ian Rogers

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=aXfeNfYgDVXhkrKM@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=leo.yan@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=shimin.guo@skydio.com \
    --cc=yujie.liu@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox