From: Masami Hiramatsu <mhiramat@kernel.org>
To: "Björn Töpel" <bjorn.topel@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Björn Töpel" <bjorn.topel@intel.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
magnus.karlsson@intel.com
Subject: Re: [PATCH] perf probe: Fix probe definition for inlined functions
Date: Thu, 22 Jun 2017 19:01:38 +0900 [thread overview]
Message-ID: <20170622190138.b9fdfaada8da0af1b8cf6990@kernel.org> (raw)
In-Reply-To: <20170621164134.5701-1-bjorn.topel@gmail.com>
On Wed, 21 Jun 2017 18:41:34 +0200
Björn Töpel <bjorn.topel@gmail.com> wrote:
> From: Björn Töpel <bjorn.topel@intel.com>
>
> In commit 613f050d68a8 ("perf probe: Fix to probe on gcc generated
> functions in modules"), the offset from symbol is, incorrectly, added
> to the trace point address. This leads to incorrect probe trace points
> for inlined functions and when using relative line number on symbols.
>
> Prior this patch:
> $ perf probe -m nf_nat -D in_range
> p:probe/in_range nf_nat:in_range.isra.9+0
> $ perf probe -m i40e -D i40e_clean_rx_irq
> p:probe/i40e_clean_rx_irq i40e:i40e_napi_poll+2212
> $ perf probe -m i40e -D i40e_clean_rx_irq:16
> p:probe/i40e_clean_rx_irq i40e:i40e_lan_xmit_frame+626
>
> After:
> $ perf probe -m nf_nat -D in_range
> p:probe/in_range nf_nat:in_range.isra.9+0
> $ perf probe -m i40e -D i40e_clean_rx_irq
> p:probe/i40e_clean_rx_irq i40e:i40e_napi_poll+1106
> $ perf probe -m i40e -D i40e_clean_rx_irq:16
> p:probe/i40e_clean_rx_irq i40e:i40e_napi_poll+2665
OK, I've confirmed it. This bug also affects -D option for
offline probes...
$ ./perf probe -k ~/kbin/linux.x86_64/vmlinux -vD vfs_read:11
probe-definition(0): vfs_read:11
[...]
Try to find probe point from debuginfo.
Matched function: vfs_read [28b211e]
Probe point found: vfs_read+90 <- here vfs_read+90
Found 1 probe_trace_events.
p:probe/vfs_read vfs_read+180 <- here vfs_read+180 = 90+90
So offset to be doubled...
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Arnaldo, this should go to urgent/stable.
Thank you!
>
> Fixes: 613f050d68a8 ("perf probe: Fix to probe on gcc generated functions in modules")
> Signed-off-by: Björn Töpel <bjorn.topel@intel.com>
> ---
> tools/perf/util/probe-event.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/probe-event.c b/tools/perf/util/probe-event.c
> index 84e7e698411e..a2670e9d652d 100644
> --- a/tools/perf/util/probe-event.c
> +++ b/tools/perf/util/probe-event.c
> @@ -619,7 +619,7 @@ static int post_process_probe_trace_point(struct probe_trace_point *tp,
> struct map *map, unsigned long offs)
> {
> struct symbol *sym;
> - u64 addr = tp->address + tp->offset - offs;
> + u64 addr = tp->address - offs;
>
> sym = map__find_symbol(map, addr);
> if (!sym)
> --
> 2.7.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2017-06-22 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 16:41 [PATCH] perf probe: Fix probe definition for inlined functions Björn Töpel
2017-06-22 10:01 ` Masami Hiramatsu [this message]
2017-06-22 16:16 ` Arnaldo Carvalho de Melo
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=20170622190138.b9fdfaada8da0af1b8cf6990@kernel.org \
--to=mhiramat@kernel.org \
--cc=acme@redhat.com \
--cc=bjorn.topel@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=magnus.karlsson@intel.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;
as well as URLs for NNTP newsgroup(s).