From: German Gomez <german.gomez@arm.com>
To: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
acme@kernel.org
Cc: German Gomez <german.gomez@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>
Subject: [PATCH 0/1] perf test: Add test for branch stack sampling
Date: Wed, 15 Jun 2022 14:09:00 +0100 [thread overview]
Message-ID: <20220615130901.1151397-1-german.gomez@arm.com> (raw)
Hi,
While testing Anshuman Khandual's branch stack sampling ABI, and BRBE
driver ([1] and [2] respectively) I've been using this test to check the
consistency between arches (x86 and Arm64).
We might extend it with Arm64-specific tests once the BRBE driver has
been reviewed and merged, but for now I think this is generic enough to
cover both x86 LBR and Arm BRBE.
Thanks,
German
[1] https://lore.kernel.org/linux-arm-kernel/20220610035101.424112-1-anshuman.khandual@arm.com/
[2] https://lore.kernel.org/all/20220613100119.684673-1-anshuman.khandual@arm.com/
German Gomez (1):
perf test: Add self test for branch stack sampling
tools/perf/tests/shell/lib/brstack/main.h | 15 ++++
tools/perf/tests/shell/lib/brstack/test.c | 25 +++++++
tools/perf/tests/shell/test_brstack.sh | 86 +++++++++++++++++++++++
3 files changed, 126 insertions(+)
create mode 100644 tools/perf/tests/shell/lib/brstack/main.h
create mode 100644 tools/perf/tests/shell/lib/brstack/test.c
create mode 100755 tools/perf/tests/shell/test_brstack.sh
--
2.25.1
next reply other threads:[~2022-06-15 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 13:09 German Gomez [this message]
2022-06-15 13:09 ` [PATCH] " German Gomez
2022-06-27 16:38 ` Ian Rogers
2022-06-27 16:45 ` German Gomez
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=20220615130901.1151397-1-german.gomez@arm.com \
--to=german.gomez@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@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
all inboxes | Powered by JetHome®