From: Thomas Meyer <thomas@m3y3r.de>
To: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
shuah@kernel.org
Cc: Thomas Meyer <thomas@m3y3r.de>
Subject: [PATCH 1/3] selftests/ftrace: multiple_kprobes: Also check for support
Date: Fri, 8 Sep 2017 14:01:17 +0200 [thread overview]
Message-ID: <20170908120119.29724-1-thomas@m3y3r.de> (raw)
The multiple_kprobes test case fails to check for KPROBE_EVENT support.
Add the check to prevent a false test result.
Signed-off-by: Thomas Meyer <thomas@m3y3r.de>
---
tools/testing/selftests/ftrace/test.d/kprobe/multiple_kprobes.tc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/testing/selftests/ftrace/test.d/kprobe/multiple_kprobes.tc b/tools/testing/selftests/ftrace/test.d/kprobe/multiple_kprobes.tc
index 2a1cb9908746..a4fd4c851a5b 100644
--- a/tools/testing/selftests/ftrace/test.d/kprobe/multiple_kprobes.tc
+++ b/tools/testing/selftests/ftrace/test.d/kprobe/multiple_kprobes.tc
@@ -1,6 +1,8 @@
#!/bin/sh
# description: Register/unregister many kprobe events
+[ -f kprobe_events ] || exit_unsupported # this is configurable
+
# ftrace fentry skip size depends on the machine architecture.
# Currently HAVE_KPROBES_ON_FTRACE defined on x86 and powerpc64le
case `uname -m` in
--
2.11.0
next reply other threads:[~2017-09-08 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 12:01 Thomas Meyer [this message]
2017-09-08 12:01 ` [PATCH 2/3] selftests/intel_pstate: No need to compile test progs in the run script Thomas Meyer
2017-09-14 14:59 ` Shuah Khan
2017-09-08 12:01 ` [PATCH 3/3] selftests/net: msg_zerocopy enable build with older kernel headers Thomas Meyer
2017-09-14 14:58 ` [PATCH 1/3] selftests/ftrace: multiple_kprobes: Also check for support Shuah Khan
2017-09-14 15:15 ` Masami Hiramatsu
2017-09-15 19:10 ` Steven Rostedt
2017-09-18 15:18 ` Steven Rostedt
2017-09-18 15:19 ` Shuah Khan
2017-09-19 14:47 ` Shuah Khan
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=20170908120119.29724-1-thomas@m3y3r.de \
--to=thomas@m3y3r.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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
all inboxes | Powered by JetHome®