public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: linux-kselftest@vger.kernel.org, shuah@kernel.org,
	Steven Rostedt <rostedt@goodmis.org>
Cc: mhiramat@kernel.org, Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 3/7] ftrace/kprobes: selftests: Check kretprobe maxactive is supported
Date: Tue, 23 May 2017 15:05:50 +0900	[thread overview]
Message-ID: <149551954028.30231.8369532850074140222.stgit@devbox> (raw)
In-Reply-To: <149551934796.30231.12544755801380678045.stgit@devbox>

Check the kretprobe maxactive is supported by kprobe_events
interface. To ensure the kernel feature, this changes ftrace
README to describe it.

Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
---
 kernel/trace/trace.c                               |    3 ++-
 .../ftrace/test.d/kprobe/kretprobe_maxactive.tc    |    1 +
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 1122f15..dc3f91e 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -4473,7 +4473,8 @@ static const char readme_msg[] =
 #endif
 #if defined(CONFIG_KPROBE_EVENTS) || defined(CONFIG_UPROBE_EVENTS)
 	"\t  accepts: event-definitions (one definition per line)\n"
-	"\t   Format: p|r[:[<group>/]<event>] <place> [<args>]\n"
+	"\t   Format: p[:[<group>/]<event>] <place> [<args>]\n"
+	"\t           r[maxactive][:[<group>/]<event>] <place> [<args>]\n"
 	"\t           -:[<group>/]<event>\n"
 #ifdef CONFIG_KPROBE_EVENTS
 	"\t    place: [<module>:]<symbol>[+<offset>]|<memaddr>\n"
diff --git a/tools/testing/selftests/ftrace/test.d/kprobe/kretprobe_maxactive.tc b/tools/testing/selftests/ftrace/test.d/kprobe/kretprobe_maxactive.tc
index 57abdf1..7ec6f26 100644
--- a/tools/testing/selftests/ftrace/test.d/kprobe/kretprobe_maxactive.tc
+++ b/tools/testing/selftests/ftrace/test.d/kprobe/kretprobe_maxactive.tc
@@ -2,6 +2,7 @@
 # description: Kretprobe dynamic event with maxactive
 
 [ -f kprobe_events ] || exit_unsupported # this is configurable
+grep -q 'r\[maxactive\]' README || exit_unsupported # this is older version
 
 echo > kprobe_events
 

  parent reply	other threads:[~2017-05-23  6:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23  6:02 [PATCH 0/7] selftests/ftrace: Some improvements of ftracetest Masami Hiramatsu
2017-05-23  6:03 ` [PATCH 1/7] selftests/ftrace: Skip full-glob-matching filter test on older kernel Masami Hiramatsu
2017-05-23  6:04 ` [PATCH 2/7] selftests/ftrace: Reduce trace buffer checking overhead Masami Hiramatsu
2017-05-23  6:05 ` Masami Hiramatsu [this message]
2017-05-23  6:06 ` [PATCH 4/7] selftests/ftrace: Reset ftrace filter on older kernel Masami Hiramatsu
2017-05-23  6:07 ` [PATCH 5/7] selftests/ftrace: Add instance indication in test log Masami Hiramatsu
2017-05-23  6:09 ` [PATCH 6/7] selftests/ftrace: Use top-level available_filter_function Masami Hiramatsu
2017-05-23  6:10 ` [PATCH 7/7] selftests/ftrace: Return unsupported if it detects older kernel Masami Hiramatsu
2017-06-07 22:42 ` [PATCH 0/7] selftests/ftrace: Some improvements of ftracetest Shuah Khan
2017-06-07 22:56   ` Steven Rostedt
2017-06-07 23:01     ` Shuah Khan
2017-06-08 17:37       ` Steven Rostedt
2017-06-08 20:06         ` Shuah Khan
2017-06-08 21:08           ` Steven Rostedt
2017-06-08 21:14             ` Shuah Khan
2017-06-08 21:26               ` Steven Rostedt
2017-06-08 21:33                 ` Shuah Khan
2017-06-08 21:39                   ` Steven Rostedt
2017-06-08 21:44                     ` Shuah Khan
2017-06-08 21:51                       ` Steven Rostedt
2017-06-14  2:12                         ` Masami Hiramatsu
2017-06-14  4:53                           ` Masami Hiramatsu
2017-06-14 14:17                             ` Shuah Khan
2017-06-30 14:18                               ` Shuah Khan
2017-06-08 21:11       ` Steven Rostedt

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=149551954028.30231.8369532850074140222.stgit@devbox \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.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