From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Thomas Falcon <thomas.falcon@intel.com>,
Leo Yan <leo.yan@arm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH v1 00/12] perf tests: Enhancements, speedups, and flakiness fixes
Date: Mon, 15 Jun 2026 18:27:32 -0700 [thread overview]
Message-ID: <20260616012744.4049193-1-irogers@google.com> (raw)
This patch series introduces a comprehensive set of improvements to the perf
test suite, focusing on execution speed, reliability, and correctness.
It contains the following key updates:
1. Speed optimizations for shell tests (lock contention, off-cpu profiling,
metrics validation) by scaling down workload durations and using lighter
system-wide defaults.
2. Fixes for test flakiness in branch stack sampling, BPF counters on hybrid
systems, Python JIT dump profiling, and trace record/replay.
3. A new robust retry helper (perf_record_with_retry) to ensure reliable
recording of intermittent events in slow or virtualized environments.
4. Support for sub-second durations in noploop and thloop workloads to
accelerate tests that only require brief sampling windows.
5. Fixes for terminal width truncation during parallel test execution, ensuring
the progress output does not wrap or corrupt the screen when test names
exceed the terminal width (including skipped tests).
6. Restrictions on core PMU bypass parsing to correctly enforce the
--pmu-filter option.
The combined changes drastically reduce the total runtime of the test suite
while improving the stability of hardware-dependent and sampling-based tests.
Ian Rogers (12):
perf parse-events: Restrict core PMU bypass to --cputype option
perf test: Truncate test description to fit terminal width
perf tests workloads: Support sub-second durations in noploop and
thloop
perf tests: Add robust record retry helper and use subsecond workloads
perf tests: Skip metrics validation if system-wide recording lacks
permission
perf tests: Fix Python JIT dump profiling test failure
perf tests: Fix flakiness in trace record and replay test
perf tests: Fix flakiness in BPF counters test on hybrid systems
perf tests: Fix flakiness in branch stack sampling tests
perf tests: Speed up off-cpu profiling tests
perf tests: Speed up lock contention analysis shell test
perf tests: Speed up metrics checking shell tests
tools/perf/builtin-stat.c | 2 +
tools/perf/tests/builtin-test.c | 95 +++++++---
tools/perf/tests/parse-events.c | 11 +-
tools/perf/tests/pmu-events.c | 6 +-
tools/perf/tests/shell/jitdump-python.sh | 66 ++++---
tools/perf/tests/shell/kvm.sh | 61 ++++---
.../tests/shell/lib/perf_metric_validation.py | 11 +-
tools/perf/tests/shell/lib/perf_record.sh | 52 ++++++
tools/perf/tests/shell/lock_contention.sh | 30 +--
tools/perf/tests/shell/pipe_test.sh | 4 +-
tools/perf/tests/shell/record.sh | 172 +++++++++---------
tools/perf/tests/shell/record_lbr.sh | 50 +++--
tools/perf/tests/shell/record_offcpu.sh | 12 +-
tools/perf/tests/shell/stat_all_metrics.sh | 65 ++++---
tools/perf/tests/shell/stat_all_pfm.sh | 2 +-
tools/perf/tests/shell/stat_bpf_counters.sh | 27 ++-
tools/perf/tests/shell/stat_metrics_values.sh | 9 +-
tools/perf/tests/shell/test_brstack.sh | 6 +-
tools/perf/tests/shell/trace_record_replay.sh | 18 +-
tools/perf/tests/workloads/noploop.c | 15 +-
tools/perf/tests/workloads/thloop.c | 14 +-
tools/perf/util/metricgroup.c | 4 +-
tools/perf/util/parse-events.c | 22 ++-
tools/perf/util/parse-events.h | 17 +-
24 files changed, 494 insertions(+), 277 deletions(-)
create mode 100644 tools/perf/tests/shell/lib/perf_record.sh
--
2.54.0.1136.gdb2ca164c4-goog
next reply other threads:[~2026-06-16 1:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 1:27 Ian Rogers [this message]
2026-06-16 1:27 ` [PATCH v1 01/12] perf parse-events: Restrict core PMU bypass to --cputype option Ian Rogers
2026-06-16 1:44 ` sashiko-bot
2026-06-16 1:27 ` [PATCH v1 02/12] perf test: Truncate test description to fit terminal width Ian Rogers
2026-06-16 1:38 ` sashiko-bot
2026-06-16 1:27 ` [PATCH v1 03/12] perf tests workloads: Support sub-second durations in noploop and thloop Ian Rogers
2026-06-16 1:35 ` sashiko-bot
2026-06-16 1:27 ` [PATCH v1 04/12] perf tests: Add robust record retry helper and use subsecond workloads Ian Rogers
2026-06-16 1:38 ` sashiko-bot
2026-06-16 1:27 ` [PATCH v1 05/12] perf tests: Skip metrics validation if system-wide recording lacks permission Ian Rogers
2026-06-16 1:41 ` sashiko-bot
2026-06-16 1:27 ` [PATCH v1 06/12] perf tests: Fix Python JIT dump profiling test failure Ian Rogers
2026-06-16 1:39 ` sashiko-bot
2026-06-16 1:27 ` [PATCH v1 07/12] perf tests: Fix flakiness in trace record and replay test Ian Rogers
2026-06-16 1:42 ` sashiko-bot
2026-06-16 1:27 ` [PATCH v1 08/12] perf tests: Fix flakiness in BPF counters test on hybrid systems Ian Rogers
2026-06-16 1:35 ` sashiko-bot
2026-06-16 1:27 ` [PATCH v1 09/12] perf tests: Fix flakiness in branch stack sampling tests Ian Rogers
2026-06-16 1:27 ` [PATCH v1 10/12] perf tests: Speed up off-cpu profiling tests Ian Rogers
2026-06-16 1:41 ` sashiko-bot
2026-06-16 1:27 ` [PATCH v1 11/12] perf tests: Speed up lock contention analysis shell test Ian Rogers
2026-06-16 1:27 ` [PATCH v1 12/12] perf tests: Speed up metrics checking shell tests Ian Rogers
-- strict thread matches above, loose matches on Subject: below --
2026-06-16 1:25 [PATCH v1 00/12] perf tests: Enhancements, speedups, and flakiness fixes Ian Rogers
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=20260616012744.4049193-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=thomas.falcon@intel.com \
--cc=tmricht@linux.ibm.com \
/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