From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH 00/11] perf test: test_intel_pt.sh: Add per-thread test
Date: Mon, 12 Sep 2022 11:34:01 +0300 [thread overview]
Message-ID: <20220912083412.7058-1-adrian.hunter@intel.com> (raw)
Hi
Here is a new per-thread test for the test_intel_pt.sh test script.
The first 9 patches are tidy-ups for the script, mostly based on results
from the shellcheck utility.
The 10th patch adds debug prints that the script will capture to help
verify correct operation.
The final patch actually adds the new test.
Adrian Hunter (11):
perf test: test_intel_pt.sh: Add cleanup function
perf test: test_intel_pt.sh: Use a temp directory
perf test: test_intel_pt.sh: Fix redirection
perf test: test_intel_pt.sh: Stop using expr
perf test: test_intel_pt.sh: Stop using backticks
perf test: test_intel_pt.sh: Use grep -c instead of grep plus wc -l
perf test: test_intel_pt.sh: Use quotes around variable expansion
perf test: test_intel_pt.sh: Fix return checking
perf test: test_intel_pt.sh: Add more output in preparation for more tests
perf tools: Add debug messages and comments for testing
perf test: test_intel_pt.sh: Add per-thread test
tools/lib/perf/evlist.c | 2 +
tools/perf/builtin-record.c | 8 +
tools/perf/tests/shell/test_intel_pt.sh | 307 ++++++++++++++++++++++++++++++--
tools/perf/util/evsel.c | 2 +
4 files changed, 304 insertions(+), 15 deletions(-)
Regards
Adrian
next reply other threads:[~2022-09-12 8:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 8:34 Adrian Hunter [this message]
2022-09-12 8:34 ` [PATCH 01/11] perf test: test_intel_pt.sh: Add cleanup function Adrian Hunter
2022-09-12 8:34 ` [PATCH 02/11] perf test: test_intel_pt.sh: Use a temp directory Adrian Hunter
2022-09-12 8:34 ` [PATCH 03/11] perf test: test_intel_pt.sh: Fix redirection Adrian Hunter
2022-09-12 8:34 ` [PATCH 04/11] perf test: test_intel_pt.sh: Stop using expr Adrian Hunter
2022-09-12 8:34 ` [PATCH 05/11] perf test: test_intel_pt.sh: Stop using backticks Adrian Hunter
2022-09-12 8:34 ` [PATCH 06/11] perf test: test_intel_pt.sh: Use grep -c instead of grep plus wc -l Adrian Hunter
2022-09-12 8:34 ` [PATCH 07/11] perf test: test_intel_pt.sh: Use quotes around variable expansion Adrian Hunter
2022-09-12 8:34 ` [PATCH 08/11] perf test: test_intel_pt.sh: Fix return checking Adrian Hunter
2022-09-12 8:34 ` [PATCH 09/11] perf test: test_intel_pt.sh: Add more output in preparation for more tests Adrian Hunter
2022-09-12 8:34 ` [PATCH 10/11] perf tools: Add debug messages and comments for testing Adrian Hunter
2022-09-12 8:34 ` [PATCH 11/11] perf test: test_intel_pt.sh: Add per-thread test Adrian Hunter
2022-09-13 17:37 ` Namhyung Kim
2022-09-13 17:41 ` [PATCH 00/11] " Namhyung Kim
2022-09-14 8:25 ` Adrian Hunter
2022-09-26 19:35 ` Arnaldo Carvalho de Melo
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=20220912083412.7058-1-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).