From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/2] A couple of small updates/fixes for kprobes tracer
Date: Thu, 22 Jun 2017 00:20:26 +0530 [thread overview]
Message-ID: <cover.1498070485.git.naveen.n.rao@linux.vnet.ibm.com> (raw)
Two simple updates for kprobes tracer:
- the first patch is a convenience and allows to probe module symbols
as well as any dot symbols (necessary on powerpc64 elfv1) without
having to provide a name for the probepoint.
- the second patch updates the newly added multiple_kprobes.tc test
case for powerpc.
Thanks,
Naveen
Naveen N. Rao (2):
trace/kprobes: Sanitize derived event names
selftests/ftrace: Update multiple kprobes test for powerpc
kernel/trace/trace_kprobe.c | 9 +++++++++
tools/testing/selftests/ftrace/test.d/kprobe/multiple_kprobes.tc | 8 ++++----
2 files changed, 13 insertions(+), 4 deletions(-)
--
2.13.1
next reply other threads:[~2017-06-21 18:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 18:50 Naveen N. Rao [this message]
2017-06-21 18:50 ` [PATCH 1/2] trace/kprobes: Sanitize derived event names Naveen N. Rao
2017-06-22 9:29 ` Masami Hiramatsu
2017-06-22 19:03 ` Naveen N. Rao
2017-06-23 17:30 ` Masami Hiramatsu
2017-06-21 18:50 ` [PATCH 2/2] selftests/ftrace: Update multiple kprobes test for powerpc Naveen N. Rao
2017-06-22 9:07 ` Masami Hiramatsu
2017-06-22 17:03 ` Naveen N. Rao
2017-06-23 17:30 ` Masami Hiramatsu
2017-06-24 11:06 ` Masami Hiramatsu
2017-06-28 9:28 ` Naveen N. Rao
2017-06-28 14:16 ` Masami Hiramatsu
2017-06-28 18:43 ` Naveen N. Rao
2017-06-29 0:57 ` Masami Hiramatsu
2017-06-29 13:08 ` Naveen N. Rao
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.1498070485.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=linuxppc-dev@lists.ozlabs.org \
--cc=mhiramat@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).