All of lore.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>, Guo Ren <guoren@kernel.org>,
	Tianyou Li <tianyou.li@intel.com>,
	Athira Rajeev <atrajeev@linux.ibm.com>,
	Stephen Brennan <stephen.s.brennan@oracle.com>,
	Aditya Bodkhe <aditya.b1@linux.ibm.com>,
	Chun-Tse Shao <ctshao@google.com>,
	Swapnil Sapkal <swapnil.sapkal@amd.com>,
	Howard Chu <howardchu95@gmail.com>,
	Sergei Trofimovich <slyich@gmail.com>,
	Shimin Guo <shimin.guo@skydio.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-csky@vger.kernel.org
Subject: Re: [PATCH v1 0/4] perf e_flags support for CSKY
Date: Mon, 26 Jan 2026 17:51:49 -0300	[thread overview]
Message-ID: <aXfT5XlRkURVMwDB@x1> (raw)
In-Reply-To: <20260123222209.1181249-1-irogers@google.com>

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

      parent reply	other threads:[~2026-01-26 20:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23 22:22 [PATCH v1 0/4] perf e_flags support for CSKY Ian Rogers
2026-01-23 22:22 ` [PATCH v1 1/4] perf dso: Factor out e_machine reading for use in thread Ian Rogers
2026-01-23 22:22 ` [PATCH v1 2/4] perf thread: Add optional e_flags output argument to thread__e_machine Ian Rogers
2026-01-23 22:22 ` [PATCH v1 3/4] perf perf_regs: Accurately compute register names for CSKY Ian Rogers
2026-01-23 22:22 ` [PATCH v1 4/4] perf unwind-libdw: Wire up e_flags " Ian Rogers
2026-01-26 20:51 ` 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=aXfT5XlRkURVMwDB@x1 \
    --to=acme@kernel.org \
    --cc=aditya.b1@linux.ibm.com \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=atrajeev@linux.ibm.com \
    --cc=ctshao@google.com \
    --cc=guoren@kernel.org \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-csky@vger.kernel.org \
    --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=slyich@gmail.com \
    --cc=stephen.s.brennan@oracle.com \
    --cc=swapnil.sapkal@amd.com \
    --cc=tianyou.li@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.