From: Masami Hiramatsu <mhiramat@redhat.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] trace_kprobes: always show group name
Date: Wed, 25 Nov 2009 07:43:39 -0500 [thread overview]
Message-ID: <4B0D267B.9060107@redhat.com> (raw)
In-Reply-To: <4B0CEBAF.6000104@cn.fujitsu.com>
Lai Jiangshan wrote:
>
> Sometimes the group name is not "kprobes",
> It'll be better if we can read it from tracing/kprobe_events.
>
> # echo 'r:laijs/vfs_read vfs_read %ax' > kprobe_events
> # cat kprobe_events
> r:laijs/vfs_read vfs_read %ax=%ax
Yep, that looks very nice :-)
Acked-by: Masami Hiramatsu <mhiramat@redhat.com>
>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> ---
> diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c
> index 79ce6a2..9e42f2a 100644
> --- a/kernel/trace/trace_kprobe.c
> +++ b/kernel/trace/trace_kprobe.c
> @@ -758,7 +758,7 @@ static int probes_seq_show(struct seq_file *m, void *v)
> char buf[MAX_ARGSTR_LEN + 1];
>
> seq_printf(m, "%c", probe_is_return(tp) ? 'r' : 'p');
> - seq_printf(m, ":%s", tp->call.name);
> + seq_printf(m, ":%s/%s", tp->call.system, tp->call.name);
>
> if (tp->symbol)
> seq_printf(m, " %s+%u", probe_symbol(tp), tp->rp.kp.offset);
>
>
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next prev parent reply other threads:[~2009-11-25 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 8:32 [PATCH 2/3] trace_kprobes: always show group name Lai Jiangshan
2009-11-25 12:43 ` Masami Hiramatsu [this message]
2009-11-27 5:50 ` [tip:perf/core] trace_kprobes: Always " tip-bot for Lai Jiangshan
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=4B0D267B.9060107@redhat.com \
--to=mhiramat@redhat.com \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.