From: James Clark <james.clark@arm.com>
To: linux-perf-users@vger.kernel.org, irogers@google.com
Cc: James Clark <james.clark@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
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>,
Spoorthy S <spoorts2@in.ibm.com>,
Kajol Jain <kjain@linux.ibm.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] perf test: Skip test_arm_callgraph_fp.sh if unwinding isn't built in
Date: Tue, 23 Jan 2024 16:39:00 +0000 [thread overview]
Message-ID: <20240123163903.350306-1-james.clark@arm.com> (raw)
The first commit outputs the unwinding feature definition in perf
version so that the script can gate on it. And then skip the test if
it's not present.
I didn't add any fixes tags because it's modifying the perf version
output, requires both commits, and it's just for a test skip change so
I don't think backporting makes sense.
James Clark (2):
perf version: Display availability of HAVE_DWARF_UNWIND_SUPPORT
perf test: Skip test_arm_callgraph_fp.sh if unwinding isn't built in
tools/perf/builtin-version.c | 1 +
tools/perf/tests/shell/test_arm_callgraph_fp.sh | 6 ++++++
2 files changed, 7 insertions(+)
--
2.34.1
next reply other threads:[~2024-01-23 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 16:39 James Clark [this message]
2024-01-23 16:39 ` [PATCH 1/2] perf version: Display availability of HAVE_DWARF_UNWIND_SUPPORT James Clark
2024-01-23 16:39 ` [PATCH 2/2] perf test: Skip test_arm_callgraph_fp.sh if unwinding isn't built in James Clark
2024-01-23 17:41 ` Ian Rogers
2024-01-24 9:24 ` James Clark
2024-01-24 18:30 ` Ian Rogers
2024-01-25 21:45 ` [PATCH 0/2] " 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=20240123163903.350306-1-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kjain@linux.ibm.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=peterz@infradead.org \
--cc=spoorts2@in.ibm.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
all inboxes | Powered by JetHome®