[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230825061125.24312-4-adityag@linux.ibm.com>
Date: Fri, 25 Aug 2023 11:41:24 +0530
From: Aditya Gupta <adityag@...ux.ibm.com>
To: acme@...nel.org, jolsa@...nel.org, irogers@...gle.com,
namhyung@...nel.org
Cc: linux-perf-users@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
maddy@...ux.ibm.com, atrajeev@...ux.vnet.ibm.com,
kjain@...ux.ibm.com, disgoel@...ux.vnet.ibm.com,
linux-kernel@...r.kernel.org
Subject: [PATCH 3/4] perf tests task_analyzer: check perf build for libtraceevent support
Currently we depend on output of 'perf record -e "sched:sched_switch"', to
check whether perf was built with libtraceevent support.
Instead, a more straightforward approach can be to check the build options,
using 'perf build --has libtraceevent', to check for libtraceevent support.
Signed-off-by: Aditya Gupta <adityag@...ux.ibm.com>
---
tools/perf/tests/shell/test_task_analyzer.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/perf/tests/shell/test_task_analyzer.sh b/tools/perf/tests/shell/test_task_analyzer.sh
index 92d15154ba79..b4803e373fe5 100755
--- a/tools/perf/tests/shell/test_task_analyzer.sh
+++ b/tools/perf/tests/shell/test_task_analyzer.sh
@@ -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 build --has libtraceevent >/dev/null && return 0
+ return 2
}
prepare_perf_data() {
--
2.41.0
Powered by blists - more mailing lists