From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Masami Hiramatsu <mhiramat@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
lkml <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Christoph Hellwig <hch@infradead.org>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Jim Keniston <jkenisto@us.ibm.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
systemtap <systemtap@sources.redhat.com>,
DLE <dle-develop@lists.sourceforge.net>
Subject: Re: [PATCH -tip tracing/kprobes 0/9] tracing/kprobes, perf: perf probe and kprobe-tracer bugfixes
Date: Tue, 20 Oct 2009 19:51:19 +0200 [thread overview]
Message-ID: <20091020175116.GD4906@nowhere> (raw)
In-Reply-To: <20091020064334.GK8550@elte.hu>
On Tue, Oct 20, 2009 at 08:43:34AM +0200, Ingo Molnar wrote:
> also useful for command line workflows: 'perf probe --list' output - i
> think we users to generate func_symbol+rel_position kind of probes.
>
> Plus a relative position is more intuitive as well. If you see
> 'schedule+10' versus 'schedule+102', you'll know it immediate that the
> first one is early in the function while the second one is near the end.
>
> If you see 'schedule@2465' versus 'schedule@2555' that kind of 'where in
> the function is the probe, roughly' subjective impression is lost.
>
> Ingo
Yeah, from a probe id reading POV, that's much better.
next prev parent reply other threads:[~2009-10-20 17:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-17 0:07 [PATCH -tip tracing/kprobes 0/9] tracing/kprobes, perf: perf probe and kprobe-tracer bugfixes Masami Hiramatsu
2009-10-17 0:07 ` [PATCH -tip tracing/kprobes 1/9] tracing/kprobes: Update kprobe-tracer selftest against new syntax Masami Hiramatsu
2009-10-17 10:04 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-10-17 0:07 ` [PATCH -tip tracing/kprobes 2/9] tracing/kprobes: Add failure messages for debugging Masami Hiramatsu
2009-10-17 10:05 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-10-17 0:07 ` [PATCH -tip tracing/kprobes 3/9] x86: Add MMX/SSE opcode groups to opcode map Masami Hiramatsu
2009-10-17 10:05 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-10-17 0:07 ` [PATCH -tip tracing/kprobes 4/9] x86: Add AMD prefetch and 3DNow! opcodes " Masami Hiramatsu
2009-10-17 10:05 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-10-17 0:07 ` [PATCH -tip tracing/kprobes 5/9] perf: Check libdwarf APIs for perf probe Masami Hiramatsu
2009-10-17 10:05 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-10-17 0:08 ` [PATCH -tip tracing/kprobes 6/9] perf: Use die() for error cases in perf-probe Masami Hiramatsu
2009-10-17 10:06 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-10-17 0:08 ` [PATCH -tip tracing/kprobes 7/9] perf: Use eprintf() for debug messages " Masami Hiramatsu
2009-10-17 10:06 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-10-17 0:08 ` [PATCH -tip tracing/kprobes 8/9] perf: Add DIE_IF() macro for error checking Masami Hiramatsu
2009-10-17 10:06 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-10-17 0:08 ` [PATCH -tip tracing/kprobes 9/9] perf: Add perf-probe document Masami Hiramatsu
2009-10-17 10:06 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-10-17 8:02 ` [PATCH -tip tracing/kprobes 0/9] tracing/kprobes, perf: perf probe and kprobe-tracer bugfixes Ingo Molnar
2009-10-17 10:34 ` Ingo Molnar
2009-10-17 10:37 ` Ingo Molnar
2009-10-18 6:01 ` Masami Hiramatsu
2009-10-19 7:51 ` Ingo Molnar
2009-10-19 11:00 ` Frederic Weisbecker
2009-10-19 11:21 ` Ingo Molnar
2009-10-19 19:32 ` Frederic Weisbecker
2009-10-20 6:43 ` Ingo Molnar
2009-10-20 17:51 ` Frederic Weisbecker [this message]
2009-10-19 19:51 ` Masami Hiramatsu
2009-10-19 22:54 ` Masami Hiramatsu
2009-10-20 6:51 ` Ingo Molnar
2009-10-21 0:05 ` Masami Hiramatsu
2009-10-20 6:50 ` Ingo Molnar
2009-10-20 14:38 ` Masami Hiramatsu
2009-10-19 16:18 ` Arnaldo Carvalho de Melo
2009-10-20 17:45 ` Frederic Weisbecker
2009-10-19 18:56 ` Masami Hiramatsu
2009-10-20 6:54 ` Ingo Molnar
2009-10-20 14:27 ` Masami Hiramatsu
2009-10-19 23:10 ` Ashwin Chaugule
2009-10-20 0:30 ` Masami Hiramatsu
2009-10-20 1:59 ` Ashwin Chaugule
2009-10-20 6:55 ` Ingo Molnar
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=20091020175116.GD4906@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=ananth@in.ibm.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=efault@gmx.de \
--cc=fche@redhat.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
--cc=systemtap@sources.redhat.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.