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 v2 0/3] perf more ELF machine usage
Date: Tue, 27 Jan 2026 01:09:12 -0300 [thread overview]
Message-ID: <aXg6aEpEl9F44vRS@x1> (raw)
In-Reply-To: <20260126220550.2573257-1-irogers@google.com>
On Mon, Jan 26, 2026 at 02:05:47PM -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.
>
> v2: Resolve conflicts with:
> https://lore.kernel.org/lkml/20260123222209.1181249-1-irogers@google.com/
>
> v1: https://lore.kernel.org/lkml/20260124001611.1332019-1-irogers@google.com/
>
> Ian Rogers (3):
> perf script: Fix script_fetch_insn for more than just x86
> perf callchain: Switch callchain_param_setup from an arch to an
> e_machine
> perf thread-stack: Switch thread_stack__init to use e_machine
Thanks, applied to perf-tools-next,
- Arnaldo
prev parent reply other threads:[~2026-01-27 4:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 22:05 [PATCH v2 0/3] perf more ELF machine usage Ian Rogers
2026-01-26 22:05 ` [PATCH v2 1/3] perf script: Fix script_fetch_insn for more than just x86 Ian Rogers
2026-01-26 22:05 ` [PATCH v2 2/3] perf callchain: Switch callchain_param_setup from an arch to an e_machine Ian Rogers
2026-01-26 22:05 ` [PATCH v2 3/3] perf thread-stack: Switch thread_stack__init to use e_machine Ian Rogers
2026-01-27 4:09 ` Arnaldo Carvalho de Melo [this message]
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=aXg6aEpEl9F44vRS@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