From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/4] A fix and a few new tests for kprobe tracer
Date: Sat, 8 Jul 2017 00:27:29 +0530 [thread overview]
Message-ID: <cover.1499453040.git.naveen.n.rao@linux.vnet.ibm.com> (raw)
v2:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1434048.html
Changes since v2:
- Update tests to include additional scenarios and better error
checking.
Thanks,
Naveen
Masami Hiramatsu (1):
selftests/ftrace: Add a testcase for kprobe event naming
Naveen N. Rao (3):
trace/kprobes: Sanitize derived event names
selftests/ftrace: Update multiple kprobes test for powerpc
selftests/ftrace: Add a test to probe module functions
kernel/trace/trace_kprobe.c | 9 ++++++
.../ftrace/test.d/kprobe/kprobe_eventname.tc | 36 ++++++++++++++++++++++
.../ftrace/test.d/kprobe/kprobe_module.tc | 28 +++++++++++++++++
.../ftrace/test.d/kprobe/multiple_kprobes.tc | 4 +--
4 files changed, 75 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/kprobe_eventname.tc
create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/kprobe_module.tc
--
2.13.2
next reply other threads:[~2017-07-07 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 18:57 Naveen N. Rao [this message]
2017-07-07 18:57 ` [PATCH v3 1/4] trace/kprobes: Sanitize derived event names Naveen N. Rao
2017-07-07 18:57 ` [PATCH v3 2/4] selftests/ftrace: Update multiple kprobes test for powerpc Naveen N. Rao
2017-07-07 18:57 ` [PATCH v3 3/4] selftests/ftrace: Add a test to probe module functions Naveen N. Rao
2017-07-07 18:57 ` [PATCH v3 4/4] selftests/ftrace: Add a testcase for kprobe event naming Naveen N. Rao
2017-07-09 11:48 ` [PATCH v3 0/4] A fix and a few new tests for kprobe tracer Steven Rostedt
2017-07-24 15:58 ` Shuah Khan
2017-07-26 21:22 ` 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=cover.1499453040.git.naveen.n.rao@linux.vnet.ibm.com \
--to=naveen.n.rao@linux.vnet.ibm.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mpe@ellerman.id.au \
--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