From: German Gomez <german.gomez@arm.com>
To: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
acme@kernel.org
Cc: james.clark@arm.com, leo.yan@linaro.org,
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: [RFC PATCH 0/1] perf test cs-etm: Add end-to-end tests for CoreSight decoding
Date: Mon, 23 May 2022 15:49:51 +0100 [thread overview]
Message-ID: <20220523144952.364370-1-german.gomez@arm.com> (raw)
Hi
While discussing running more tests for CoreSight, we thought it might
be a good idea to upstream some EndToEnd tests for CoreSight decoding in
order to lock down the behaviour. I am sending this as RFC to get some
feedback from the community first.
The test relies on pre-geneated perf.data files that are downloaded
during the test. I'm not sure it's a good idea to commit those files to
the Linux repository, so they would have to live in an external source
and be downloaded during the test.
For this RFC, the files are stored in a Github repository [1]. As an
idea, I think we could store them in a new repo in the ARM-software
namespace. Any hosting suggestions are very welcome.
Thanks,
German
[1] https://github.com/ARM-software/data/tree/984cde8fb0bb22591e284826a80b338bb79c3655/perf/coresight
German Gomez (1):
perf test cs-etm: Add end-to-end tests for CoreSight decoding
tools/perf/tests/shell/lib/arm_auxtrace.sh | 21 +++++++
.../tests/shell/test_arm_coresight_decoder.sh | 57 +++++++++++++++++++
2 files changed, 78 insertions(+)
create mode 100644 tools/perf/tests/shell/lib/arm_auxtrace.sh
create mode 100755 tools/perf/tests/shell/test_arm_coresight_decoder.sh
--
2.25.1
next reply other threads:[~2022-05-23 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 14:49 German Gomez [this message]
2022-05-23 14:49 ` [RFC PATCH 1/1] " German Gomez
2022-05-23 20:04 ` [RFC PATCH 0/1] " Arnaldo Carvalho de Melo
2022-05-23 21:29 ` Ian Rogers
2022-05-24 13: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=20220523144952.364370-1-german.gomez@arm.com \
--to=german.gomez@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@linaro.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®