[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260209202208.2027001-1-irogers@google.com>
Date: Mon, 9 Feb 2026 12:22:05 -0800
From: Ian Rogers <irogers@...gle.com>
To: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>, Namhyung Kim <namhyung@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>, Jiri Olsa <jolsa@...nel.org>,
Ian Rogers <irogers@...gle.com>, Adrian Hunter <adrian.hunter@...el.com>,
James Clark <james.clark@...aro.org>, Sandipan Das <sandipan.das@....com>, Leo Yan <leo.yan@....com>,
Yujie Liu <yujie.liu@...el.com>, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org
Subject: [PATCH v1 0/3] perf script engine testing
Add tests for generating a script and that the basic APIs work. I'd
grown concerned that refactoring patches may inadvertently break perf
script engine support, particularly for perl, and this does something
to prevent this.
Ian Rogers (3):
perf script: Allow the generated script to be a path
perf test script: Add perl script testing support
perf test script: Add python script testing support
tools/perf/Documentation/perf-script.txt | 6 +-
tools/perf/builtin-script.c | 24 ++++-
tools/perf/tests/shell/script_perl.sh | 102 ++++++++++++++++++++
tools/perf/tests/shell/script_python.sh | 113 +++++++++++++++++++++++
4 files changed, 239 insertions(+), 6 deletions(-)
create mode 100755 tools/perf/tests/shell/script_perl.sh
create mode 100755 tools/perf/tests/shell/script_python.sh
--
2.53.0.rc2.204.g2597b5adb4-goog
Powered by blists - more mailing lists