From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Sandipan Das <sandipan.das@amd.com>, Leo Yan <leo.yan@arm.com>,
Yujie Liu <yujie.liu@intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1 0/3] perf script engine testing
Date: Wed, 11 Feb 2026 13:44:22 -0300 [thread overview]
Message-ID: <aYyx5i62BAShcOcS@x1> (raw)
In-Reply-To: <20260209202208.2027001-1-irogers@google.com>
On Mon, Feb 09, 2026 at 12:22:05PM -0800, Ian Rogers wrote:
> 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.
Thanks, tested and applied to perf-tools-next,
- Arnaldo
> 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
>
prev parent reply other threads:[~2026-02-11 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 20:22 [PATCH v1 0/3] perf script engine testing Ian Rogers
2026-02-09 20:22 ` [PATCH v1 1/3] perf script: Allow the generated script to be a path Ian Rogers
2026-02-09 20:22 ` [PATCH v1 2/3] perf test script: Add perl script testing support Ian Rogers
2026-02-09 20:22 ` [PATCH v1 3/3] perf test script: Add python " Ian Rogers
2026-02-11 16:44 ` Arnaldo Carvalho de Melo [this message]
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=aYyx5i62BAShcOcS@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.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=sandipan.das@amd.com \
--cc=yujie.liu@intel.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