From: Sandipan Das <sandipan.das@amd.com>
To: <linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>, <x86@kernel.org>
Cc: <peterz@infradead.org>, <bp@alien8.de>, <acme@kernel.org>,
<namhyung@kernel.org>, <jolsa@kernel.org>, <tglx@linutronix.de>,
<mingo@redhat.com>, <mark.rutland@arm.com>,
<alexander.shishkin@linux.intel.com>,
<dave.hansen@linux.intel.com>, <james.clark@arm.com>,
<irogers@google.com>, <eranian@google.com>, <maddy@linux.ibm.com>,
<kjain@linux.ibm.com>, <tmricht@linux.ibm.com>,
<ananth.narayan@amd.com>, <ravi.bangoria@amd.com>,
<santosh.shukla@amd.com>, <sandipan.das@amd.com>
Subject: [PATCH v4 0/4] tools perf: Add branch speculation info
Date: Thu, 2 Feb 2023 17:56:13 +0530 [thread overview]
Message-ID: <cover.1675333809.git.sandipan.das@amd.com> (raw)
AMD Last Branch Record Extension Version 2 (LbrExtV2) provides branch
speculation information and the perf UAPI is extended to provide this in
a generic way. Make perf tool show this additional information.
The UAPI changes can be found in commit 93315e46b000 ("perf/core: Add
speculation info to branch entries").
Requesting help from folks having access to big-endian systems to test
changes in the sample parsing test as I was only able to test these in
a ppc64 simulator.
Previous versions can be found at:
v3: https://lore.kernel.org/all/cover.1675057032.git.sandipan.das@amd.com/
v2: https://lore.kernel.org/all/cover.1664356751.git.sandipan.das@amd.com/
v1: https://lore.kernel.org/all/cover.1660217326.git.sandipan.das@amd.com/
Changes in v4:
- Update tests that were failing due to changes in perf output and
sample parsing (thanks to Arnaldo for reporting).
Changes in v3:
- Drop tools-side UAPI changes as they have already been added by other
commits.
- Rebase on top of latest perf/core.
Changes in v2:
- Drop msr-index.h related changes for now.
- Rebase on top of latest perf/core.
- Fix UAPI breakage introduced by the ARM64 BRBE changes to perf branch
entry.
Sandipan Das (4):
perf script: Show branch speculation info
perf session: Show branch speculation info in raw dump
perf test sample-parsing: Update expected branch flags
perf test brstack: Update regex to include spec field
tools/perf/builtin-script.c | 5 +++--
tools/perf/tests/sample-parsing.c | 2 +-
tools/perf/tests/shell/test_brstack.sh | 18 +++++++++---------
tools/perf/util/branch.c | 15 +++++++++++++++
tools/perf/util/branch.h | 2 ++
tools/perf/util/evsel.c | 15 ++++++++++++---
tools/perf/util/session.c | 5 +++--
7 files changed, 45 insertions(+), 17 deletions(-)
--
2.34.1
next reply other threads:[~2023-02-02 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 12:26 Sandipan Das [this message]
2023-02-02 12:26 ` [PATCH v4 1/4] perf script: Show branch speculation info Sandipan Das
2023-02-02 12:26 ` [PATCH v4 2/4] perf session: Show branch speculation info in raw dump Sandipan Das
2023-02-02 12:26 ` [PATCH v4 3/4] perf test sample-parsing: Update expected branch flags Sandipan Das
2023-02-02 12:26 ` [PATCH v4 4/4] perf test brstack: Update regex to include spec field Sandipan Das
2023-02-02 13:04 ` [PATCH v4 0/4] tools perf: Add branch speculation info Arnaldo Carvalho de Melo
2023-02-02 13:10 ` Arnaldo Carvalho de Melo
2023-02-02 13:14 ` Sandipan Das
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=cover.1675333809.git.sandipan.das@amd.com \
--to=sandipan.das@amd.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=santosh.shukla@amd.com \
--cc=tglx@linutronix.de \
--cc=tmricht@linux.ibm.com \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).