From: Matt Turner <mattst88@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>
Cc: linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org,
Matt Turner <mattst88@gmail.com>
Subject: [PATCH 0/2] perf alpha: Decode ProfileMe samples
Date: Wed, 28 Oct 2026 14:10:23 -0400 [thread overview]
Message-ID: <20261028-perf-alpha-profileme-v1-0-f46c1938d001@gmail.com> (raw)
The Alpha kernel series "alpha/perf: add ProfileMe sampling" adds
ProfileMe sampling to the Alpha cpu PMU. Each ProfileMe sample carries
the profiled instruction's PMPC and its I_STAT and PCTR_CTL status as
PERF_SAMPLE_RAW data, which says whether the instruction retired,
whether it trapped and why, whether it was a mispredicted branch,
stalled before map, or was killed on a wrong path, and what PCTR1
counted while it was in flight:
https://lore.kernel.org/r/20261028-alpha-profileme-v1-0-d44b52bf2500@gmail.com
This series is the perf tool side. Patch 1 decodes the raw data in perf
report -D and perf script -D, as is done for AMD IBS. It copies the new
uapi header from the kernel series into tools/arch, so it should wait
until that header is merged. Patch 2 adds a script that sums the status
by symbol or by instruction, in the style of DCPI.
To try it, with the kernel series applied:
perf record -R -e instructions:p -- ./workload
tools/perf/python/alpha-profileme.py --pc
I tested this on an AlphaServer ES47 (EV7). Sampling a loop whose
branch tests random data reports that branch mispredicted in 21% of its
samples, and 0% with sorted data.
Signed-off-by: Matt Turner <mattst88@gmail.com>
---
Matt Turner (2):
perf alpha: Decode ProfileMe raw samples
perf python: Add alpha-profileme.py
tools/arch/alpha/include/uapi/asm/perf_event.h | 27 +++++
tools/perf/check-headers.sh | 1 +
tools/perf/python/alpha-profileme.py | 162 +++++++++++++++++++++++++
tools/perf/util/Build | 1 +
tools/perf/util/alpha-sample-raw.c | 133 ++++++++++++++++++++
tools/perf/util/sample-raw.c | 2 +
tools/perf/util/sample-raw.h | 2 +
7 files changed, 328 insertions(+)
---
base-commit: e74880764bf94b738102b4b6b6e8304d0c8375d3
change-id: 20261028-perf-alpha-profileme-8010299be323
Best regards,
--
Matt Turner <mattst88@gmail.com>
next reply other threads:[~2026-10-28 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 18:10 Matt Turner [this message]
2026-10-28 18:10 ` [PATCH 1/2] perf alpha: Decode ProfileMe raw samples Matt Turner
2026-10-28 18:10 ` [PATCH 2/2] perf python: Add alpha-profileme.py Matt Turner
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=20261028-perf-alpha-profileme-v1-0-f46c1938d001@gmail.com \
--to=mattst88@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®