From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: He Kuang <hekuang@huawei.com>
Cc: acme@kernel.org, a.p.zijlstra@chello.nl, mingo@redhat.com,
namhyung@kernel.org, wangnan0@huawei.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] perf probe: Set retprobe flag when probe in address-based alternative mode
Date: Tue, 14 Apr 2015 00:42:52 +0900 [thread overview]
Message-ID: <552BE3FC.5060307@hitachi.com> (raw)
In-Reply-To: <1428925290-5623-1-git-send-email-hekuang@huawei.com>
(2015/04/13 20:41), He Kuang wrote:
> Perf probe misses to set retprobe flag back when falling back to
> address-based alternative mode.
>
> Can be reproduced as following:
>
> $ perf probe -v -k vmlinux --add='sys_write%return'
> ...
> Added new event:
> Writing event: p:probe/sys_write _stext+1584952
> probe:sys_write (on sys_write%return)
>
> $ cat /sys/kernel/debug/tracing/kprobe_events
> p:probe/sys_write _stext+1584952
>
> After this patch:
>
> $ perf probe -v -k vmlinux --add='sys_write%return'
> Added new event:
> Writing event: r:probe/sys_write SyS_write+0
> probe:sys_write (on sys_write%return)
>
> $ cat /sys/kernel/debug/tracing/kprobe_events
> r:probe/sys_write SyS_write
>
> Signed-off-by: He Kuang <hekuang@huawei.com>
Oops, I missed that!
Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Thank you!
> ---
> tools/perf/util/probe-event.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
> index 30545ce..5483d98 100644
> --- a/tools/perf/util/probe-event.c
> +++ b/tools/perf/util/probe-event.c
> @@ -332,6 +332,7 @@ static int find_alternative_probe_point(struct debuginfo *dinfo,
> else {
> result->offset += pp->offset;
> result->line += pp->line;
> + result->retprobe = pp->retprobe;
> ret = 0;
> }
>
>
--
Masami HIRAMATSU
Linux Technology Research Center, System Productivity Research Dept.
Center for Technology Innovation - Systems Engineering
Hitachi, Ltd., Research & Development Group
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2015-04-13 15:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 11:41 [PATCH 1/3] perf probe: Set retprobe flag when probe in address-based alternative mode He Kuang
2015-04-13 11:41 ` [PATCH 2/3] perf probe: Make --source avaiable when probe with lazy_line He Kuang
2015-04-13 15:41 ` Masami Hiramatsu
2015-04-13 16:05 ` Arnaldo Carvalho de Melo
2015-04-13 20:56 ` Arnaldo Carvalho de Melo
2015-04-13 20:57 ` Arnaldo Carvalho de Melo
2015-04-13 21:00 ` Arnaldo Carvalho de Melo
2015-04-13 11:41 ` [PATCH 3/3] perf probe: Fix segfault when probe with lazy_line to file He Kuang
2015-04-13 16:03 ` Masami Hiramatsu
2015-04-14 12:18 ` [tip:perf/urgent] " tip-bot for He Kuang
2015-04-13 14:39 ` [PATCH 1/3] perf probe: Set retprobe flag when probe in address-based alternative mode Arnaldo Carvalho de Melo
2015-04-13 14:42 ` Arnaldo Carvalho de Melo
2015-04-13 15:38 ` He Kuang
2015-04-13 20:42 ` Arnaldo Carvalho de Melo
2015-04-13 15:23 ` He Kuang
2015-04-13 16:23 ` Arnaldo Carvalho de Melo
2015-04-13 15:42 ` Masami Hiramatsu [this message]
2015-04-13 16:05 ` Arnaldo Carvalho de Melo
2015-04-14 12:17 ` [tip:perf/urgent] " tip-bot for He Kuang
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=552BE3FC.5060307@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=hekuang@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=wangnan0@huawei.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