Skip to contentSkip to conversation

Introduce perf check subcommand

PATCH Superseded Aditya Gupta 2 participants 9 messages Sep 3, 2023 – Sep 12, 2023 perf events

v1 of 15 Superseded Latest is v15 →

lore
Share & tools
lore
#0 lore raw

cover Introduce perf check subcommand

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/[email protected]/

Introduce a subcommand "perf check --feature", with which scripts can test for presence of a feature, such as:

    perf check --feature HAVE_LIBTRACEEVENT

    or

    perf check --feature libtraceevent

The usage of "perf version --build-options | grep" has been replaced in two tests, with "perf check --feature" 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 check --feature' 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-check-feature

Changelog
=========
V1
+ changed subcommand name to 'perf check --feature'
+ added documentation for perf check
+ support both macro (eg. HAVE_LIBTRACEEVENT), and name (eg. libtraceevent) as input to 'perf check --feature'
+ change subject and descriptions of all patch mentioning perf check instead of perf build

V0: Previous patch series: https://lore.kernel.org/linux-perf-users/[email protected]/

Aditya Gupta (3):
perf check: introduce check subcommand
perf version: update --build-options to use 'supported_features' array perf tests task_analyzer: use perf check for libtraceevent support

Athira Rajeev (1):
tools/perf/tests: Update probe_vfs_getname.sh script to use perf check
--feature

 tools/perf/Build                              |  1 +
 tools/perf/Documentation/perf-check.txt       | 53 +++++++++++
 tools/perf/builtin-check.c                    | 95 +++++++++++++++++++
 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 +-
 10 files changed, 217 insertions(+), 37 deletions(-)
 create mode 100644 tools/perf/Documentation/perf-check.txt
 create mode 100644 tools/perf/builtin-check.c
Signature · 1 line
2.41.0
#1 lore raw

PATCH 1/4 perf check: introduce check subcommand

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"

Instead of this, introduce a subcommand "perf check --feature", with which scripts can test for presence of a feature, such as:

    perf check --feature HAVE_FEATURE

'perf check --feature' command is expected to have exit status of 1 if feature is built-in, and 0 if not, -2 if feature is not known.

A global array 'supported_features' has also been introduced that can be used by other commands like 'perf version --build-options', so that new features can be added in one place, with the array

---
 tools/perf/Build                        |  1 +
 tools/perf/Documentation/perf-check.txt | 53 ++++++++++++++
 tools/perf/builtin-check.c              | 95 +++++++++++++++++++++++++
 tools/perf/builtin.h                    | 47 ++++++++++++
 tools/perf/perf.c                       |  1 +
 5 files changed, 197 insertions(+)
 create mode 100644 tools/perf/Documentation/perf-check.txt
 create mode 100644 tools/perf/builtin-check.c
tools/perf/Build +1 -0
index aa7623622834..a55a797c1b5f 100644
@@ -1,5 +1,6 @@
 perf-y += builtin-bench.o
 perf-y += builtin-annotate.o
+perf-y += builtin-check.o
 perf-y += builtin-config.o
 perf-y += builtin-diff.o
 perf-y += builtin-evlist.o
tools/perf/Documentation/perf-check.txt new file +53 -0

53 lines not on this page · raw message

tools/perf/builtin-check.c new file +95 -0

95 lines not on this page · raw message

tools/perf/builtin.h +47 -0

59 lines not on this page · raw message

tools/perf/perf.c +1 -0
index d3fc8090413c..83dc0ac42fdb 100644
@@ -50,6 +50,7 @@ static struct cmd_struct commands[] = {
 	{ "archive",	NULL,	0 },
 	{ "buildid-cache", cmd_buildid_cache, 0 },
 	{ "buildid-list", cmd_buildid_list, 0 },
+	{ "check", cmd_check, 0 },
 	{ "config",	cmd_config,	0 },
 	{ "c2c",	cmd_c2c,	0 },
 	{ "diff",	cmd_diff,	0 },
Signature · 1 line
2.41.0
maintainer
#2 lore raw

Re: [PATCH 1/4] perf check: introduce check subcommand

Hello,

Quoted 173 lines · Aditya Gupta

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"

Instead of this, introduce a subcommand "perf check --feature", with which scripts can test for presence of a feature, such as:

    perf check --feature HAVE_FEATURE

'perf check --feature' command is expected to have exit status of 1 if feature is built-in, and 0 if not, -2 if feature is not known.

A global array 'supported_features' has also been introduced that can be used by other commands like 'perf version --build-options', so that new features can be added in one place, with the array

---
 tools/perf/Build                        |  1 +
 tools/perf/Documentation/perf-check.txt | 53 ++++++++++++++
 tools/perf/builtin-check.c              | 95 +++++++++++++++++++++++++
 tools/perf/builtin.h                    | 47 ++++++++++++
 tools/perf/perf.c                       |  1 +
 5 files changed, 197 insertions(+)
 create mode 100644 tools/perf/Documentation/perf-check.txt
 create mode 100644 tools/perf/builtin-check.c
tools/perf/Build +1 -0
index aa7623622834..a55a797c1b5f 100644
@@ -1,5 +1,6 @@
 perf-y += builtin-bench.o
 perf-y += builtin-annotate.o
+perf-y += builtin-check.o
 perf-y += builtin-config.o
 perf-y += builtin-diff.o
 perf-y += builtin-evlist.o
tools/perf/Documentation/perf-check.txt new file +53 -0
new file mode 100644
index 000000000000..ee4331838be5
@@ -0,0 +1,53 @@
+perf-check(1)
+===============
+
+NAME
+----
+perf-check - check features in perf
+
+SYNOPSIS
+--------
+'perf check' [--feature]
+
+DESCRIPTION
+-----------
+With no options given, the 'perf check' just prints the perf version
+on the standard output.
+
+If the option '--feature' is given, then status of feature is printed
+on the standard output, ie. whether it is compiled-in/built-in or not
+
+OPTIONS
+-------
+--feature::
+        Print whether a feature is compiled-in or not. A feature name/macro is
+        required to be passed after this flag
+
+        Example Usage:
+                perf check --feature libtraceevent
+                perf check --feature HAVE_LIBTRACEEVENT
+
+        Supported feature names/macro:
+                dwarf      /  HAVE_DWARF_SUPPORT
+                dwarf_getlocations  /  HAVE_DWARF_GETLOCATIONS_SUPPORT
+                libaudit   /  HAVE_LIBAUDIT_SUPPORT
+                syscall_table       /  HAVE_SYSCALL_TABLE_SUPPORT
+                libbfd     /  HAVE_LIBBFD_SUPPORT
+                debuginfod /  HAVE_DEBUGINFOD_SUPPORT
+                libelf     /  HAVE_LIBELF_SUPPORT
+                libnuma    /  HAVE_LIBNUMA_SUPPORT
+                numa_num_possible_cpus  /  HAVE_LIBNUMA_SUPPORT
+                libperl    /  HAVE_LIBPERL_SUPPORT
+                libpython  /  HAVE_LIBPYTHON_SUPPORT
+                libslang   /  HAVE_SLANG_SUPPORT
+                libcrypto  /  HAVE_LIBCRYPTO_SUPPORT
+                libunwind  /  HAVE_LIBUNWIND_SUPPORT
+                libdw-dwarf-unwind  /  HAVE_DWARF_SUPPORT
+                zlib       /  HAVE_ZLIB_SUPPORT
+                lzma       /  HAVE_LZMA_SUPPORT
+                get_cpuid  /  HAVE_AUXTRACE_SUPPORT
+                bpf        /  HAVE_LIBBPF_SUPPORT
+                aio        /  HAVE_AIO_SUPPORT
+                zstd       /  HAVE_ZSTD_SUPPORT
+                libpfm4    /  HAVE_LIBPFM
+                libtraceevent      /  HAVE_LIBTRACEEVENT
tools/perf/builtin-check.c new file +68 -0
new file mode 100644
index 000000000000..3dee72426c30
@@ -0,0 +1,95 @@
+// SPDX-License-Identifier: GPL-2.0
+#include "builtin.h"
+#include "color.h"
+#include "util/debug.h"
+#include "util/header.h"
+#include <tools/config.h>
+#include <stdbool.h>
+#include <stdio.h>
+#include <string.h>
+#include <subcmd/parse-options.h>
+
+struct check {
+       const char *feature;
+};
+
+static struct check check;
+
+static struct option check_options[] = {
+       OPT_STRING(0, "feature", &check.feature, NULL, "check if a feature is built in"),
+       OPT_END(),
+};
+
+static const char * const check_usage[] = {
+       "perf check [<options>]",
+       NULL
+};
+
+static void on_off_print(const char *status)
+{
+       printf("[ ");
+
+       if (!strcmp(status, "OFF"))
+               color_fprintf(stdout, PERF_COLOR_RED, "%-3s", status);
+       else
+               color_fprintf(stdout, PERF_COLOR_GREEN, "%-3s", status);
+
+       printf(" ]");
+}
+
+static void status_print(const char *name, const char *macro,
+                        const char *status)
+{
+       printf("%22s: ", name);
+       on_off_print(status);
+       printf("  # %s\n", macro);
+}
+
+#define STATUS(feature)                                   \
+do {                                                      \
+       if (feature.is_builtin)                               \
+               status_print(feature.name, feature.macro, "on");  \
+       else                                                  \
+               status_print(feature.name, feature.macro, "OFF"); \
+} while (0)
+
+/**
+ * check whether "feature" is built-in with perf
+ * returns:./perf annotate --data-type --type-stat -k vmlinux -d '[kernel.kallsyms]' --objdump=llvm-objdump
+ *   -1: Feature not known
+ *    0: Built-in
+ *    1: NOT Built in
+ */
+static int has_support(const char *feature)
+{
+       int res = -1;
+
+       for (int i = 0; supported_features[i].name; ++i) {
+               if ((strcmp(feature, supported_features[i].name) == 0) ||

tools/perf/builtin-check.c line 78

Quoted 10 lines
tools/perf/builtin-check.c new file +10 -0
+                       (strcmp(feature, supported_features[i].macro) == 0)) {
+                       res = supported_features[i].is_builtin;
+                       STATUS(supported_features[i]);
+                       break;
+               }
+       }
+
+       if (res == -1) {
+               color_fprintf(stdout, PERF_COLOR_RED, "Feature not known: %s", feature);
+               return -2;

return -1 ?? It doesn't match with the comment.

Quoted 31 lines
tools/perf/builtin-check.c new file +17 -0
+       }
+
+       return !res;
+}
+
+int cmd_check(int argc, const char **argv)
+{
+       argc = parse_options(argc, argv, check_options, check_usage,
+                            PARSE_OPT_STOP_AT_NON_OPTION);
+
+       printf("perf check %s\n", perf_version_string);
+
+       if (check.feature)
+               return has_support(check.feature);
+
+       return 0;
+}
tools/perf/builtin.h +6 -0
index f2ab5bae2150..6683ea6d3b60 100644
@@ -2,6 +2,52 @@
 #ifndef BUILTIN_H
 #define BUILTIN_H
 
+#include <stddef.h>
+#include <linux/compiler.h>
+#include <tools/config.h>
+
+struct feature_support {
+       const char *name;

tools/perf/builtin.h line 20

Quoted 10 lines
tools/perf/builtin.h +10 -0
+       const char *macro;
+       int is_builtin;
+};
+
+#define FEATURE_SUPPORT(name_, macro_) { \
+       .name = name_,                       \
+       .macro = #macro_,                    \
+       .is_builtin = IS_BUILTIN(macro_) }
+
+static struct feature_support supported_features[] __maybe_unused = {

Hmm.. do you want it in a header file?
I'm afraid it'd duplicate the entire array for any .c files that include this header.

tools/perf/builtin.h line 23

Quoted 3 lines
tools/perf/builtin.h +3 -0
+       FEATURE_SUPPORT("dwarf", HAVE_DWARF_SUPPORT),
+       FEATURE_SUPPORT("dwarf_getlocations", HAVE_DWARF_GETLOCATIONS_SUPPORT),
+#ifndef HAVE_SYSCALL_TABLE_SUPPORT

Do we really need this #ifndef?

Thanks,
Namhyung

Quoted 53 lines
tools/perf/builtin.h +28 -0
+       FEATURE_SUPPORT("libaudit", HAVE_LIBAUDIT_SUPPORT),
+#endif
+       FEATURE_SUPPORT("syscall_table", HAVE_SYSCALL_TABLE_SUPPORT),
+       FEATURE_SUPPORT("libbfd", HAVE_LIBBFD_SUPPORT),
+       FEATURE_SUPPORT("debuginfod", HAVE_DEBUGINFOD_SUPPORT),
+       FEATURE_SUPPORT("libelf", HAVE_LIBELF_SUPPORT),
+       FEATURE_SUPPORT("libnuma", HAVE_LIBNUMA_SUPPORT),
+       FEATURE_SUPPORT("numa_num_possible_cpus", HAVE_LIBNUMA_SUPPORT),
+       FEATURE_SUPPORT("libperl", HAVE_LIBPERL_SUPPORT),
+       FEATURE_SUPPORT("libpython", HAVE_LIBPYTHON_SUPPORT),
+       FEATURE_SUPPORT("libslang", HAVE_SLANG_SUPPORT),
+       FEATURE_SUPPORT("libcrypto", HAVE_LIBCRYPTO_SUPPORT),
+       FEATURE_SUPPORT("libunwind", HAVE_LIBUNWIND_SUPPORT),
+       FEATURE_SUPPORT("libdw-dwarf-unwind", HAVE_DWARF_SUPPORT),
+       FEATURE_SUPPORT("zlib", HAVE_ZLIB_SUPPORT),
+       FEATURE_SUPPORT("lzma", HAVE_LZMA_SUPPORT),
+       FEATURE_SUPPORT("get_cpuid", HAVE_AUXTRACE_SUPPORT),
+       FEATURE_SUPPORT("bpf", HAVE_LIBBPF_SUPPORT),
+       FEATURE_SUPPORT("aio", HAVE_AIO_SUPPORT),
+       FEATURE_SUPPORT("zstd", HAVE_ZSTD_SUPPORT),
+       FEATURE_SUPPORT("libpfm4", HAVE_LIBPFM),
+       FEATURE_SUPPORT("libtraceevent", HAVE_LIBTRACEEVENT),
+
+       // this should remain at end, to know the array end
+       FEATURE_SUPPORT(NULL, _)
+};
+
 void list_common_cmds_help(void);
 const char *help_unknown_cmd(const char *cmd);
 
@@ -9,6 +55,7 @@ int cmd_annotate(int argc, const char **argv);
 int cmd_bench(int argc, const char **argv);
 int cmd_buildid_cache(int argc, const char **argv);
 int cmd_buildid_list(int argc, const char **argv);
+int cmd_check(int argc, const char **argv);
 int cmd_config(int argc, const char **argv);
 int cmd_c2c(int argc, const char **argv);
 int cmd_diff(int argc, const char **argv);
tools/perf/perf.c +1 -1
index d3fc8090413c..83dc0ac42fdb 100644
@@ -50,6 +50,7 @@ static struct cmd_struct commands[] = {
        { "archive",    NULL,   0 },
        { "buildid-cache", cmd_buildid_cache, 0 },
        { "buildid-list", cmd_buildid_list, 0 },
+       { "check", cmd_check, 0 },
        { "config",     cmd_config,     0 },
        { "c2c",        cmd_c2c,        0 },
        { "diff",       cmd_diff,       0 },
--

2.41.0

#3 lore raw

Re: [PATCH 1/4] perf check: introduce check subcommand

Hello Namhyung,
Sorry for the late reply, was busy last week.

Quoted 23 lines · Namhyung Kim

Hello,

Quoted 20 lines · Aditya Gupta

...

tools/perf/builtin-check.c new file +17 -0
+/**
+ * check whether "feature" is built-in with perf
+ * returns:./perf annotate --data-type --type-stat -k vmlinux -d '[kernel.kallsyms]' --objdump=llvm-objdump
+ *   -1: Feature not known
+ *    0: Built-in
+ *    1: NOT Built in
+ */
+static int has_support(const char *feature)
+{
+       int res = -1;
+
+       for (int i = 0; supported_features[i].name; ++i) {
+               if ((strcmp(feature, supported_features[i].name) == 0) ||
+                       (strcmp(feature, supported_features[i].macro) == 0)) {
+                       res = supported_features[i].is_builtin;
+                       STATUS(supported_features[i]);
+                       break;
Quoted 9 lines

tools/perf/builtin-check.c line 78

Quoted 6 lines
tools/perf/builtin-check.c new file +6 -0
+               }
+       }
+
+       if (res == -1) {
+               color_fprintf(stdout, PERF_COLOR_RED, "Feature not known: %s", feature);
+               return -2;

return -1 ?? It doesn't match with the comment.

Thanks for pointing this. Yes, it should have returned -1, I made a mistake in this.

Quoted 38 lines
Quoted 38 lines
tools/perf/builtin-check.c new file +17 -0
+       }
+
+       return !res;
+}
+
+int cmd_check(int argc, const char **argv)
+{
+       argc = parse_options(argc, argv, check_options, check_usage,
+                            PARSE_OPT_STOP_AT_NON_OPTION);
+
+       printf("perf check %s\n", perf_version_string);
+
+       if (check.feature)
+               return has_support(check.feature);
+
+       return 0;
+}
tools/perf/builtin.h +12 -0
index f2ab5bae2150..6683ea6d3b60 100644
@@ -2,6 +2,52 @@
 #ifndef BUILTIN_H
 #define BUILTIN_H
 
+#include <stddef.h>
+#include <linux/compiler.h>
+#include <tools/config.h>
+
+struct feature_support {
+       const char *name;
+       const char *macro;
+       int is_builtin;
+};
+
+#define FEATURE_SUPPORT(name_, macro_) { \
+       .name = name_,                       \
Quoted 9 lines

tools/perf/builtin.h line 20

Quoted 4 lines
tools/perf/builtin.h +4 -0
+       .macro = #macro_,                    \
+       .is_builtin = IS_BUILTIN(macro_) }
+
+static struct feature_support supported_features[] __maybe_unused = {

Hmm.. do you want it in a header file?
I'm afraid it'd duplicate the entire array for any .c files that include this header.

Hmm.. I agree that it duplicates the array in all those c files.

Should I define 'supported_features' same way in perf.c, and then use 'extern struct feature_support supported_features[]' in builtin.h ?

Quoted 6 lines

tools/perf/builtin.h line 23

Quoted 4 lines
tools/perf/builtin.h +3 -0
+       FEATURE_SUPPORT("dwarf", HAVE_DWARF_SUPPORT),
+       FEATURE_SUPPORT("dwarf_getlocations", HAVE_DWARF_GETLOCATIONS_SUPPORT),
+#ifndef HAVE_SYSCALL_TABLE_SUPPORT

Do we really need this #ifndef?

Not really, will remove this in next version. It was this way in 'perf version --build-options' so I just kept it that way.

Thanks,
Aditya Gupta

#4 lore raw

PATCH 2/4 perf version: update --build-options to use 'supported_features' array

In reply to Aditya Gupta

Now that the feature list has been duplicated in a global 'supported_features' array, use that array instead of manually checking status of built-in features.

This helps in being consistent with commands such as 'perf check --feature', so commands can use the same array, and any new feature can be added at one place, in the 'supported_features' array

---
 tools/perf/builtin-version.c | 39 ++++++++----------------------------
 1 file changed, 8 insertions(+), 31 deletions(-)
tools/perf/builtin-version.c +8 -31
index e5859c70e195..e149d96c6dc5 100644
@@ -46,41 +46,18 @@ static void status_print(const char *name, const char *macro,
 	printf("  # %s\n", macro);
 }
 
-#define STATUS(__d, __m)				\
-do {							\
-	if (IS_BUILTIN(__d))				\
-		status_print(#__m, #__d, "on");		\
-	else						\
-		status_print(#__m, #__d, "OFF");	\
+#define STATUS(feature)                                   \
+do {                                                      \
+	if (feature.is_builtin)                               \
+		status_print(feature.name, feature.macro, "on");  \
+	else                                                  \
+		status_print(feature.name, feature.macro, "OFF"); \
 } while (0)
 
 static void library_status(void)
 {
-	STATUS(HAVE_DWARF_SUPPORT, dwarf);
-	STATUS(HAVE_DWARF_GETLOCATIONS_SUPPORT, dwarf_getlocations);
-#ifndef HAVE_SYSCALL_TABLE_SUPPORT
-	STATUS(HAVE_LIBAUDIT_SUPPORT, libaudit);
-#endif
-	STATUS(HAVE_SYSCALL_TABLE_SUPPORT, syscall_table);
-	STATUS(HAVE_LIBBFD_SUPPORT, libbfd);
-	STATUS(HAVE_DEBUGINFOD_SUPPORT, debuginfod);
-	STATUS(HAVE_LIBELF_SUPPORT, libelf);
-	STATUS(HAVE_LIBNUMA_SUPPORT, libnuma);
-	STATUS(HAVE_LIBNUMA_SUPPORT, numa_num_possible_cpus);
-	STATUS(HAVE_LIBPERL_SUPPORT, libperl);
-	STATUS(HAVE_LIBPYTHON_SUPPORT, libpython);
-	STATUS(HAVE_SLANG_SUPPORT, libslang);
-	STATUS(HAVE_LIBCRYPTO_SUPPORT, libcrypto);
-	STATUS(HAVE_LIBUNWIND_SUPPORT, libunwind);
-	STATUS(HAVE_DWARF_SUPPORT, libdw-dwarf-unwind);
-	STATUS(HAVE_ZLIB_SUPPORT, zlib);
-	STATUS(HAVE_LZMA_SUPPORT, lzma);
-	STATUS(HAVE_AUXTRACE_SUPPORT, get_cpuid);
-	STATUS(HAVE_LIBBPF_SUPPORT, bpf);
-	STATUS(HAVE_AIO_SUPPORT, aio);
-	STATUS(HAVE_ZSTD_SUPPORT, zstd);
-	STATUS(HAVE_LIBPFM, libpfm4);
-	STATUS(HAVE_LIBTRACEEVENT, libtraceevent);
+	for (int i = 0; supported_features[i].name; ++i)
+		STATUS(supported_features[i]);
 }
 
 int cmd_version(int argc, const char **argv)
Signature · 1 line
2.41.0
#5 lore raw

PATCH 3/4 perf tests task_analyzer: use perf check for libtraceevent support

In reply to Aditya Gupta

Currently we use output of 'perf version --build-options', to check whether perf was built with libtraceevent support.

Instead, use 'perf check --feature libtraceevent' to check for libtraceevent support.

---
 tools/perf/tests/shell/test_task_analyzer.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
tools/perf/tests/shell/test_task_analyzer.sh +2 -2
index 92d15154ba79..8fbc33c95025 100755
@@ -52,8 +52,8 @@ find_str_or_fail() {
 
 # check if perf is compiled with libtraceevent support
 skip_no_probe_record_support() {
-	perf version --build-options | grep -q " OFF .* HAVE_LIBTRACEEVENT" && return 2
-	return 0
+	perf check --feature libtraceevent >/dev/null && return 0
+	return 2
 }
 
 prepare_perf_data() {
Signature · 1 line
2.41.0
maintainer
#6 lore raw

Re: [PATCH 3/4] perf tests task_analyzer: use perf check for libtraceevent support

Quoted 17 lines · Aditya Gupta

Currently we use output of 'perf version --build-options', to check whether perf was built with libtraceevent support.

Instead, use 'perf check --feature libtraceevent' to check for libtraceevent support.

---
 tools/perf/tests/shell/test_task_analyzer.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
tools/perf/tests/shell/test_task_analyzer.sh +0 -0
index 92d15154ba79..8fbc33c95025 100755

tools/perf/tests/shell/test_task_analyzer.sh find_str_or_fail() { · line 55

Quoted 6 lines
tools/perf/tests/shell/test_task_analyzer.sh +1 -2
@@ -52,8 +52,8 @@ find_str_or_fail() {
 
 # check if perf is compiled with libtraceevent support
 skip_no_probe_record_support() {
-       perf version --build-options | grep -q " OFF .* HAVE_LIBTRACEEVENT" && return 2
-       return 0
+       perf check --feature libtraceevent >/dev/null && return 0

Maybe we can add -q/--quiet option to silent messages.

Thanks,
Namhyung

Quoted 7 lines
tools/perf/tests/shell/test_task_analyzer.sh +1 -1
+       return 2
 }
 
 prepare_perf_data() {
--

2.41.0

#7 lore raw

Re: [PATCH 3/4] perf tests task_analyzer: use perf check for libtraceevent support

Hi Namhyung,
Sorry for the late reply.

Quoted 19 lines · Namhyung Kim
Quoted 18 lines · Aditya Gupta

Currently we use output of 'perf version --build-options', to check whether perf was built with libtraceevent support.

Instead, use 'perf check --feature libtraceevent' to check for libtraceevent support.

---
 tools/perf/tests/shell/test_task_analyzer.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
tools/perf/tests/shell/test_task_analyzer.sh +0 -0
index 92d15154ba79..8fbc33c95025 100755
@@ -52,8 +52,8 @@ find_str_or_fail() {
 
Quoted 7 lines

tools/perf/tests/shell/test_task_analyzer.sh find_str_or_fail() { · line 55

Quoted 5 lines
tools/perf/tests/shell/test_task_analyzer.sh +1 -2
 # check if perf is compiled with libtraceevent support
 skip_no_probe_record_support() {
-       perf version --build-options | grep -q " OFF .* HAVE_LIBTRACEEVENT" && return 2
-       return 0
+       perf check --feature libtraceevent >/dev/null && return 0

Maybe we can add -q/--quiet option to silent messages.

Nice idea, thanks. Will do so.

Thanks
- Aditya Gupta

#8 lore raw

PATCH 4/4 tools/perf/tests: Update probe_vfs_getname.sh script to use perf check --feature

In reply to Aditya Gupta

From: Athira Rajeev <[email protected]>

In probe_vfs_getname.sh, current we use "perf record --dry-run" to check for libtraceevent and skip the test if perf is not build with libtraceevent. Change the check to use "perf check --feature" option

---
 tools/perf/tests/shell/lib/probe_vfs_getname.sh           | 4 ++--
 tools/perf/tests/shell/record+probe_libc_inet_pton.sh     | 5 ++++-
 tools/perf/tests/shell/record+script_probe_vfs_getname.sh | 5 ++++-
 3 files changed, 10 insertions(+), 4 deletions(-)
tools/perf/tests/shell/lib/probe_vfs_getname.sh +2 -2
index bf4c1fb71c4b..347106cc8988 100644
@@ -27,7 +27,7 @@ skip_if_no_debuginfo() {
 # check if perf is compiled with libtraceevent support
 skip_no_probe_record_support() {
 	if [ $had_vfs_getname -eq 1 ] ; then
-		perf record --dry-run -e $1 2>&1 | grep "libtraceevent is necessary for tracepoint support" && return 2
-		return 1
+		perf check --feature libtraceevent >/dev/null && return 1
+		return 2
 	fi
 }
tools/perf/tests/shell/record+probe_libc_inet_pton.sh +4 -1
index 89214a6d9951..0c00e94b83ff 100755
@@ -58,7 +58,10 @@ trace_libc_inet_pton_backtrace() {
 
 	# Check presence of libtraceevent support to run perf record
 	skip_no_probe_record_support "$event_name/$eventattr/"
-	[ $? -eq 2 ] && return 2
+	if [ $? -eq 2 ]; then
+		echo "WARN: Skipping test trace_libc_inet_pton_backtrace. No libtraceevent support."
+		return 2
+	fi
 
 	perf record -e $event_name/$eventattr/ -o $perf_data ping -6 -c 1 ::1 > /dev/null 2>&1
 	# check if perf data file got created in above step.
tools/perf/tests/shell/record+script_probe_vfs_getname.sh +4 -1
index 7f664f1889d9..c7416d21fc92 100755
@@ -19,7 +19,10 @@ record_open_file() {
 	echo "Recording open file:"
 	# Check presence of libtraceevent support to run perf record
 	skip_no_probe_record_support "probe:vfs_getname*"
-	[ $? -eq 2 ] && return 2
+	if [ $? -eq 2 ]; then
+		echo "WARN: Skipping test record_open_file. No libtraceevent support"
+		return 2
+	fi
 	perf record -o ${perfdata} -e probe:vfs_getname\* touch $file
 }
 
Signature · 1 line
2.41.0