From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>, Jiri Olsa <jolsa@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ian Rogers <irogers@google.com>,
linux-perf-users@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>
Subject: [PATCHSET 0/6] perf test: Improve perf record tests (v1)
Date: Tue, 6 Sep 2022 23:46:39 -0700 [thread overview]
Message-ID: <20220907064645.1197894-1-namhyung@kernel.org> (raw)
Hello,
This patchset improves the perf record tests to check more cases so
that it can find problems early. The motivation is a failure in
per-thread mmap with multi-threaded targets which Adrian is working on
the fix.
I added a custom test program and more combinations like system-wide
and command line workload (in per-process mode) testing with
multi-threaded recording mode.
Currently it fails on per-thread and register capture tests. The
system-wide test was skipped since I ran it as a normal user. We can
use this to verify Adirian's fix and future works.
$ ./perf test -v 86
86: perf record tests :
--- start ---
test child forked, pid 1190747
Build a test program
Basic --per-thread mode test
Per-thread record [Failed record]
Register capture test
Register capture test [Failed missing output]
Basic --system-wide mode test
System-wide record [Skipped not supported]
Basic target workload test
Basic target workload test [Success]
test child finished with -1
---- end ----
perf record tests: FAILED!
You can find it in 'perf/record-test-v1' branch in
git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
Thanks,
Namhyung
Namhyung Kim (6):
perf test: Do not use instructions:u explicitly
perf test: Use a test program in perf record tests
perf test: Test record with --threads option
perf test: Add system-wide mode in perf record tests
perf test: Add target workload test in perf record tests
perf test: Do not set TEST_SKIP for record subtests
tools/perf/tests/shell/record.sh | 150 +++++++++++++++++++++++++++----
1 file changed, 133 insertions(+), 17 deletions(-)
base-commit: 6c3bd8d3e01d9014312caa52e4ef1c29d5249648
--
2.37.2.789.g6183377224-goog
next reply other threads:[~2022-09-07 6:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 6:46 Namhyung Kim [this message]
2022-09-07 6:46 ` [PATCH 1/6] perf test: Do not use instructions:u explicitly Namhyung Kim
2022-09-07 7:56 ` Adrian Hunter
2022-09-07 6:46 ` [PATCH 2/6] perf test: Use a test program in perf record tests Namhyung Kim
2022-09-07 10:44 ` Adrian Hunter
2022-09-07 17:38 ` Namhyung Kim
2022-09-07 13:16 ` Adrian Hunter
2022-09-07 13:24 ` Adrian Hunter
2022-09-07 17:40 ` Namhyung Kim
2022-09-07 6:46 ` [PATCH 3/6] perf test: Test record with --threads option Namhyung Kim
2022-09-07 13:33 ` Adrian Hunter
2022-09-07 17:41 ` Namhyung Kim
2022-09-07 6:46 ` [PATCH 4/6] perf test: Add system-wide mode in perf record tests Namhyung Kim
2022-09-07 15:20 ` Adrian Hunter
2022-09-07 6:46 ` [PATCH 5/6] perf test: Add target workload test " Namhyung Kim
2022-09-13 11:03 ` Adrian Hunter
2022-09-13 17:28 ` Namhyung Kim
2022-09-07 6:46 ` [PATCH 6/6] perf test: Do not set TEST_SKIP for record subtests Namhyung Kim
2022-09-13 11:28 ` Adrian Hunter
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=20220907064645.1197894-1-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@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®