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 3/3] trace_kprobes: don't output zero offset
Date: Wed, 25 Nov 2009 08:00:37 -0500 [thread overview]
Message-ID: <4B0D2A75.9000009@redhat.com> (raw)
In-Reply-To: <4B0CEBCB.7080309@cn.fujitsu.com>
Hi Lai,
Lai Jiangshan wrote:
>
> "symbol_name+0" is not so friendly.
> It makes the output longer.
Hmm, I've added +0 just for convenience of parser programs.
But anyway, skipping it is not so costly option for them :-)
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 9e42f2a..e82bea3 100644
> --- a/kernel/trace/trace_kprobe.c
> +++ b/kernel/trace/trace_kprobe.c
> @@ -243,7 +243,11 @@ static int probe_arg_string(char *buf, size_t n, struct fetch_func *ff)
> ret = snprintf(buf, n, "@0x%p", ff->data);
> else if (ff->func == fetch_symbol) {
> struct symbol_cache *sc = ff->data;
> - ret = snprintf(buf, n, "@%s%+ld", sc->symbol, sc->offset);
> + if (sc->offset)
> + ret = snprintf(buf, n, "@%s%+ld", sc->symbol,
> + sc->offset);
> + else
> + ret = snprintf(buf, n, "@%s", sc->symbol);
> } else if (ff->func == fetch_retvalue)
> ret = snprintf(buf, n, "$retval");
> else if (ff->func == fetch_stack_address)
> @@ -760,10 +764,12 @@ static int probes_seq_show(struct seq_file *m, void *v)
> seq_printf(m, "%c", probe_is_return(tp) ? 'r' : 'p');
> seq_printf(m, ":%s/%s", tp->call.system, tp->call.name);
>
> - if (tp->symbol)
> + if (!tp->symbol)
> + seq_printf(m, " 0x%p", tp->rp.kp.addr);
> + else if (tp->rp.kp.offset)
> seq_printf(m, " %s+%u", probe_symbol(tp), tp->rp.kp.offset);
> else
> - seq_printf(m, " 0x%p", tp->rp.kp.addr);
> + seq_printf(m, " %s", probe_symbol(tp));
>
> for (i = 0; i < tp->nr_args; i++) {
> ret = probe_arg_string(buf, MAX_ARGSTR_LEN, &tp->args[i].fetch);
>
>
--
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:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 8:33 [PATCH 3/3] trace_kprobes: don't output zero offset Lai Jiangshan
2009-11-25 13:00 ` Masami Hiramatsu [this message]
2009-11-27 5:50 ` [tip:perf/core] trace_kprobes: Don't " 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=4B0D2A75.9000009@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.