From: Shuah Khan <shuah@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>, Ingo Molnar <mingo@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, "Luis R . Rodriguez" <mcgrof@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] selftests/ftrace: Add a testcase for many kprobe events
Date: Fri, 2 Jun 2017 15:37:09 -0600 [thread overview]
Message-ID: <3358257f-4428-d598-6aed-f7076ca524a5@kernel.org> (raw)
In-Reply-To: <149577388470.11702.11832460851769204511.stgit@devbox>
On 05/25/2017 10:44 PM, Masami Hiramatsu wrote:
> Add a testcase to test kprobes via ftrace interface
> with many concurrent kprobe events.
>
> This tries to add many kprobe events (up to 256) on
> kernel functions. To avoid making ftrace-based
> kprobes (kprobes on fentry), it skips first N bytes
> (on x86 N=5, on ppc or arm N=4) of function entry.
> After that, it enables all those events, disable it,
> and remove it.
>
> Since the unoptimization buffer reclaiming will
> be delayed, after removing events, it will wait
> enough time.
>
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> Suggested-by: Steven Rostedt <rostedt@goodmis.org>
Thanks. Applied to linux-kselftest next for 4.13-rc1
-- Shuah
> ---
> This ensures following bug is fixed and no regression.
>
> https://lkml.org/lkml/2017/5/25/218
> ---
> .../ftrace/test.d/kprobe/multiple_kprobes.tc | 21 ++++++++++++++++++++
> 1 file changed, 21 insertions(+)
> create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/multiple_kprobes.tc
>
> diff --git a/tools/testing/selftests/ftrace/test.d/kprobe/multiple_kprobes.tc b/tools/testing/selftests/ftrace/test.d/kprobe/multiple_kprobes.tc
> new file mode 100644
> index 0000000..f4d1ff7
> --- /dev/null
> +++ b/tools/testing/selftests/ftrace/test.d/kprobe/multiple_kprobes.tc
> @@ -0,0 +1,21 @@
> +#!/bin/sh
> +# description: Register/unregister many kprobe events
> +
> +# ftrace fentry skip size depends on the machine architecture.
> +# Currently HAVE_KPROBES_ON_FTRACE defined on x86 and powerpc
> +case `uname -m` in
> + x86_64|i[3456]86) OFFS=5;;
> + ppc*) OFFS=4;;
> + *) OFFS=0;;
> +esac
> +
> +echo "Setup up to 256 kprobes"
> +grep t /proc/kallsyms | cut -f3 -d" " | grep -v .*\\..* | \
> +head -n 256 | while read i; do echo p ${i}+${OFFS} ; done > kprobe_events ||:
> +
> +echo 1 > events/kprobes/enable
> +echo 0 > events/kprobes/enable
> +echo > kprobe_events
> +echo "Waiting for unoptimizing & freeing"
> +sleep 5
> +echo "Done"
>
>
>
prev parent reply other threads:[~2017-06-02 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 10:38 [BUGFIX PATCH] kprobes/x86: Fix to set RWX bits correctly before releasing trampoline Masami Hiramatsu
2017-05-25 17:24 ` Luis R. Rodriguez
2017-05-26 0:24 ` Masami Hiramatsu
2017-05-28 1:46 ` Jessica Yu
2017-06-01 18:26 ` Luis R. Rodriguez
2017-05-26 4:44 ` [PATCH] selftests/ftrace: Add a testcase for many kprobe events Masami Hiramatsu
2017-06-02 21:37 ` Shuah Khan [this message]
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=3358257f-4428-d598-6aed-f7076ca524a5@kernel.org \
--to=shuah@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@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®