From: Aditya Gupta <adityag@linux.ibm.com>
To: acme@kernel.org, jolsa@kernel.org, irogers@google.com,
namhyung@kernel.org
Cc: linux-perf-users@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
maddy@linux.ibm.com, atrajeev@linux.vnet.ibm.com,
kjain@linux.ibm.com, disgoel@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] Introduce perf build subcommand
Date: Fri, 25 Aug 2023 11:41:21 +0530 [thread overview]
Message-ID: <20230825061125.24312-1-adityag@linux.ibm.com> (raw)
The Problem
===========
Currently the presence of a feature is checked with a combination of
perf version --build-options and greps, such as:
perf version --build-options | grep " on .* HAVE_FEATURE"
Proposed solution
=================
As suggested by contributors in:
https://lore.kernel.org/linux-perf-users/ZMPWk5K63tadmDlU@kernel.org/
Introduce a subcommand "perf build --has", with which
scripts can test for presence of a feature, such as:
perf build --has HAVE_FEATURE
The usage of "perf version --build-options | grep" has been replaced in two
tests, with "perf build --has" command
Also, to not duplicate the same feature list at multiple places, a new global
'supported_features' array has been introduced in builtin.h, so both commands
'perf build --has' and 'perf version --build-options' use the same array
'supported_features' feature is an array of 'struct feature_support', which
also has the name of the feature, macro used to test it's presence, and a
is_builtin member, which will be 0 if feature not built-in, and 1 if built-in
Architectures Tested
====================
* x86_64
* ppc64le
Git tree
========
Git tree with this patch series applied for testing:
https://github.com/adi-g15-ibm/linux/tree/perf-build-has
Aditya Gupta (3):
perf build: introduce build subcommand
perf version: update --build-options to use 'supported_features' array
perf tests task_analyzer: check perf build for libtraceevent support
Athira Rajeev (1):
tools/perf/tests: Update probe_vfs_getname.sh script to use perf build
--has
tools/perf/Build | 1 +
tools/perf/builtin-build.c | 94 +++++++++++++++++++
tools/perf/builtin-version.c | 39 ++------
tools/perf/builtin.h | 47 ++++++++++
tools/perf/perf.c | 1 +
.../perf/tests/shell/lib/probe_vfs_getname.sh | 4 +-
.../shell/record+probe_libc_inet_pton.sh | 5 +-
.../shell/record+script_probe_vfs_getname.sh | 5 +-
tools/perf/tests/shell/test_task_analyzer.sh | 4 +-
9 files changed, 163 insertions(+), 37 deletions(-)
create mode 100644 tools/perf/builtin-build.c
--
2.41.0
next reply other threads:[~2023-08-25 6:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 6:11 Aditya Gupta [this message]
2023-08-25 6:11 ` [PATCH 1/4] perf build: introduce build subcommand Aditya Gupta
2023-08-25 6:11 ` [PATCH 2/4] perf version: update --build-options to use 'supported_features' array Aditya Gupta
2023-08-25 6:11 ` [PATCH 3/4] perf tests task_analyzer: check perf build for libtraceevent support Aditya Gupta
2023-08-25 6:11 ` [PATCH 4/4] tools/perf/tests: Update probe_vfs_getname.sh script to use perf build --has Aditya Gupta
2023-08-25 17:07 ` [PATCH 0/4] Introduce perf build subcommand Namhyung Kim
2023-08-27 7:17 ` Aditya Gupta
2023-09-03 11:53 ` Aditya Gupta
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=20230825061125.24312-1-adityag@linux.ibm.com \
--to=adityag@linux.ibm.com \
--cc=acme@kernel.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=disgoel@linux.vnet.ibm.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=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=namhyung@kernel.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).