From: Leo Yan <leo.yan@linaro.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Cc: Leo Yan <leo.yan@linaro.org>
Subject: [PATCH v3 0/2] perf test: Add test for java symbol
Date: Sun, 25 Sep 2022 10:58:33 +0800 [thread overview]
Message-ID: <20220925025835.70364-1-leo.yan@linaro.org> (raw)
This patch set is to add a test for java symbol.
To allow a shell script to know the installed lib path, we need to
export the environment variable "PREFIX" in the C code. We use the
first patch for this purpose. The second patch introduces the java
symbol testing.
The test has been verified on x86_64 machine with perf/core branch with
the latest commit 62e64c9d2fd1 ("perf test: Add basic core_wide
expression test").
Changes from v2:
- Skipped test if jshell is not existed (Namhyung);
- Fixed a typo for s/if/elif/ (Namhyung).
Changes from v1:
- Added Ian's suggested tag;
- Added the search folder for the system lib libperf-jvmti.so;
- Skip the test if fail to find jvmti lib.
Leo Yan (2):
perf subcmd: Set environment variable "PREFIX"
perf test: Introduce script for java symbol testing
tools/lib/subcmd/exec-cmd.c | 3 +
tools/perf/tests/shell/test_java_symbol.sh | 75 ++++++++++++++++++++++
2 files changed, 78 insertions(+)
create mode 100755 tools/perf/tests/shell/test_java_symbol.sh
--
2.34.1
next reply other threads:[~2022-09-25 2:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 2:58 Leo Yan [this message]
2022-09-25 2:58 ` [PATCH v3 1/2] perf subcmd: Set environment variable "PREFIX" Leo Yan
2022-09-25 2:58 ` [PATCH v3 2/2] perf test: Introduce script for java symbol testing Leo Yan
2022-09-26 19:56 ` [PATCH v3 0/2] perf test: Add test for java symbol Arnaldo Carvalho de Melo
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=20220925025835.70364-1-leo.yan@linaro.org \
--to=leo.yan@linaro.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@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).