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>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Kan Liang" <kan.liang@linux.intel.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Jiapeng Chong" <jiapeng.chong@linux.alibaba.com>,
"James Clark" <james.clark@linaro.org>,
"Howard Chu" <howardchu95@gmail.com>,
"Weilin Wang" <weilin.wang@intel.com>,
"Stephen Brennan" <stephen.s.brennan@oracle.com>,
"Andi Kleen" <ak@linux.intel.com>,
"Dmitry Vyukov" <dvyukov@google.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 5/6] perf test intel-pt: Skip jitdump test if no libelf
Date: Wed, 28 May 2025 09:52:13 -0300 [thread overview]
Message-ID: <aDcG_RVzA4d5FY2R@x1> (raw)
In-Reply-To: <20250527180703.129336-6-irogers@google.com>
On Tue, May 27, 2025 at 11:07:02AM -0700, Ian Rogers wrote:
> jitdump support is only present if building with libelf. Skip the
> intel-pt jitdump test if perf isn't compiled with libelf support.
Thanks, applied to perf-tools-next,
- Arnaldo
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/perf/tests/shell/test_intel_pt.sh | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/tools/perf/tests/shell/test_intel_pt.sh b/tools/perf/tests/shell/test_intel_pt.sh
> index f3a9a040bacc..32a9b8dcb200 100755
> --- a/tools/perf/tests/shell/test_intel_pt.sh
> +++ b/tools/perf/tests/shell/test_intel_pt.sh
> @@ -288,6 +288,11 @@ test_jitdump()
> jitdump_incl_dir="${script_dir}/../../util"
> jitdump_h="${jitdump_incl_dir}/jitdump.h"
>
> + if ! perf check feature -q libelf ; then
> + echo "SKIP: libelf is needed for jitdump"
> + return 2
> + fi
> +
> if [ ! -e "${jitdump_h}" ] ; then
> echo "SKIP: Include file jitdump.h not found"
> return 2
> --
> 2.49.0.1204.g71687c7c1d-goog
next prev parent reply other threads:[~2025-05-28 12:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 18:06 [PATCH v1 0/6] Various asan and test fixes Ian Rogers
2025-05-27 18:06 ` [PATCH v1 1/6] perf symbol: Fix use-after-free in filename__read_build_id Ian Rogers
2025-05-28 12:48 ` Arnaldo Carvalho de Melo
2025-05-27 18:06 ` [PATCH v1 2/6] perf test demangle-java: Don't segv if demangling fails Ian Rogers
2025-05-28 12:49 ` Arnaldo Carvalho de Melo
2025-05-27 18:07 ` [PATCH v1 3/6] perf symbol: Move demangling code out of symbol-elf.c Ian Rogers
2025-05-28 12:47 ` Arnaldo Carvalho de Melo
2025-05-28 18:03 ` Ian Rogers
2025-05-27 18:07 ` [PATCH v1 4/6] perf intel-tpebs: Avoid race when evlist is being deleted Ian Rogers
2025-05-28 12:51 ` Arnaldo Carvalho de Melo
2025-05-27 18:07 ` [PATCH v1 5/6] perf test intel-pt: Skip jitdump test if no libelf Ian Rogers
2025-05-28 12:52 ` Arnaldo Carvalho de Melo [this message]
2025-05-27 18:07 ` [PATCH v1 6/6] perf test trace_summary: Skip --bpf-summary tests if no libbpf 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=aDcG_RVzA4d5FY2R@x1 \
--to=acme@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alex.gaynor@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=dvyukov@google.com \
--cc=gary@garyguo.net \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jiapeng.chong@linux.alibaba.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=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=stephen.s.brennan@oracle.com \
--cc=tmgross@umich.edu \
--cc=weilin.wang@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;
as well as URLs for NNTP newsgroup(s).