From: Masami Hiramatsu <mhiramat@redhat.com>
To: Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
lkml <linux-kernel@vger.kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Jim Keniston <jkenisto@us.ibm.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
Jason Baron <jbaron@redhat.com>,
"K.Prasad" <prasad@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
systemtap <systemtap@sources.redhat.com>,
DLE <dle-develop@lists.sourceforge.net>
Subject: [PATCH -tip perf/probes 0/5] perf-probe and kprobe-tracer updates
Date: Tue, 03 Nov 2009 19:12:04 -0500 [thread overview]
Message-ID: <20091104001204.3454.75999.stgit@harusame> (raw)
Hi,
Here are some updates according to previous LKML threads.
- Update perf-probe document.
- Improve error messages.
- Fall back to non-dwarf mode if possible.
- Change group name to probe.
- Rename kprobe-tracer to kprobe-event.
BTW, I think perf-probe and kprobe-event might better share
similar syntax for not confusing users. And for that purpose,
perf-probe syntax should introduce event/group specifier,
for example,
perf probe "newgroup:newevnt=func:10 arg1 arg2"
adds the newevent under newgroup. On the other hand, ftrace
users can also add a new event as below;
echo 'newgroup:newevent=func+0x18 arg1=$a1 arg2=$a2' > kprobe_events
Any thoughts?
TODO:
- Support --list option to show probes.
- Support --del option to remove probes.
- Simplify probe names.
- Support --line option to show which lines user can probe.
- Support lazy string matching.
Thank you,
---
Masami Hiramatsu (5):
tracing/kprobes: Rename Kprobe-tracer to kprobe-event
perf/probes: Rename perf probe events group name
perf/probes: Fall back to non-dwarf if possible
perf/probes: Improve error messages
perf/probe: Update Documentation/perf-probe.txt
Documentation/trace/kprobetrace.txt | 34 ++++++-------
kernel/trace/Kconfig | 19 ++++---
kernel/trace/Makefile | 2 -
kernel/trace/trace_kprobe.c | 6 +-
tools/perf/Documentation/perf-probe.txt | 17 +++---
tools/perf/builtin-probe.c | 84 ++++++++++++++++++-------------
tools/perf/util/probe-finder.c | 7 ++-
7 files changed, 95 insertions(+), 74 deletions(-)
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next reply other threads:[~2009-11-04 0:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 0:12 Masami Hiramatsu [this message]
2009-11-04 0:12 ` [PATCH -tip perf/probes 1/5] perf/probe: Update Documentation/perf-probe.txt Masami Hiramatsu
2009-11-04 15:24 ` [tip:perf/probes] perf/probes: " tip-bot for Masami Hiramatsu
2009-11-04 0:12 ` [PATCH -tip perf/probes 2/5] perf/probes: Improve error messages Masami Hiramatsu
2009-11-04 15:25 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-11-04 0:12 ` [PATCH -tip perf/probes 3/5] perf/probes: Fall back to non-dwarf if possible Masami Hiramatsu
2009-11-04 15:25 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-11-04 0:12 ` [PATCH -tip perf/probes 4/5] perf/probes: Rename perf probe events group name Masami Hiramatsu
2009-11-04 15:25 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-11-04 0:12 ` [PATCH -tip perf/probes 5/5] tracing/kprobes: Rename Kprobe-tracer to kprobe-event Masami Hiramatsu
2009-11-04 15:25 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-11-04 2:15 ` [PATCH -tip perf/probes 0/5] perf-probe and kprobe-tracer updates Frederic Weisbecker
2009-11-04 14:11 ` Masami Hiramatsu
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=20091104001204.3454.75999.stgit@harusame \
--to=mhiramat@redhat.com \
--cc=ananth@in.ibm.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=jbaron@redhat.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=systemtap@sources.redhat.com \
/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®