From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: [PATCH 0/4] perf test: Assorted fixes and updates
Date: Fri, 28 Feb 2025 20:02:48 -0800 [thread overview]
Message-ID: <20250301040252.1586750-1-namhyung@kernel.org> (raw)
Hello,
This is a list of random fixes and updates in perf test. I've added a
new test case for perf trace and updated perf stat output test to
check the --metric-only option. Also make perf probe and trace tests
for non-root users as they need priviledged operations.
Maybe we need to fix perf stat --metric-only output not to include
bogus metrics like GHz, but let's keep it for later. :)
Thanks,
Namhyung
Namhyung Kim (4):
perf test: Add --metric-only to perf stat output tests
perf test: Skip perf probe tests when running as non-root
perf test: Skip perf trace tests when running as non-root
perf test: Add trace record and replay test
.../tests/shell/lib/perf_json_output_lint.py | 7 +++++++
tools/perf/tests/shell/lib/stat_output.sh | 8 +++++++
.../tests/shell/perftool-testsuite_probe.sh | 1 +
tools/perf/tests/shell/probe_vfs_getname.sh | 1 +
.../shell/record+probe_libc_inet_pton.sh | 1 +
.../shell/record+script_probe_vfs_getname.sh | 1 +
tools/perf/tests/shell/stat+csv_output.sh | 2 ++
tools/perf/tests/shell/stat+json_output.sh | 9 ++++++++
tools/perf/tests/shell/stat+std_output.sh | 8 +++++++
.../shell/test_uprobe_from_different_cu.sh | 11 +++++-----
.../tests/shell/trace+probe_vfs_getname.sh | 1 +
tools/perf/tests/shell/trace_btf_enum.sh | 1 +
tools/perf/tests/shell/trace_btf_general.sh | 1 +
tools/perf/tests/shell/trace_exit_race.sh | 1 +
tools/perf/tests/shell/trace_record_replay.sh | 21 +++++++++++++++++++
15 files changed, 68 insertions(+), 6 deletions(-)
create mode 100755 tools/perf/tests/shell/trace_record_replay.sh
--
2.48.1.711.g2feabab25a-goog
next reply other threads:[~2025-03-01 4:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 4:02 Namhyung Kim [this message]
2025-03-01 4:02 ` [PATCH 1/4] perf test: Add --metric-only to perf stat output tests Namhyung Kim
2025-03-01 4:02 ` [PATCH 2/4] perf test: Skip perf probe tests when running as non-root Namhyung Kim
2025-03-05 17:45 ` Arnaldo Carvalho de Melo
2025-03-05 17:52 ` Namhyung Kim
2025-03-01 4:02 ` [PATCH 3/4] perf test: Skip perf trace " Namhyung Kim
2025-03-05 17:46 ` Arnaldo Carvalho de Melo
2025-03-01 4:02 ` [PATCH 4/4] perf test: Add trace record and replay test Namhyung Kim
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=20250301040252.1586750-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=kan.liang@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).