From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Benjamin King <benjaminking@web.de>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Brendan Gregg <brendan.d.gregg@gmail.com>,
"linux-perf-use." <linux-perf-users@vger.kernel.org>,
cti.systems-productivity-manager.ts@hitachi.com
Subject: Re: Re: perf probe an addr without debuginfo
Date: Tue, 30 Jun 2015 17:51:48 +0900 [thread overview]
Message-ID: <559258A4.2020205@hitachi.com> (raw)
In-Reply-To: <20150630064457.GA20873@localhost>
On 2015/06/30 15:44, Benjamin King wrote:
> On Mon, Jun 29, 2015 at 12:00:38PM -0300, Arnaldo Carvalho de Melo wrote:
>> Em Sun, Jun 28, 2015 at 05:46:51PM +0200, Benjamin King escreveu:
>>>> Is there a trick to getting perf to probe a user-level address without
>>>> debuginfo? Eg (on Linux 4.0):
>>>> [...]
>>>> I can do this using ftrace ok, eg, "p:tick_0x583 /root/tick:0x583"
>>>> works. Thanks,
>>>
>>> Not quite what you have asked for, but you can add the probe via ftrace and
>>> then use it from perf. Probes from /sys/kernel/debug/tracing/uprobe_events
>>> will show up in 'perf list' as well.
>>
>> Masami,
>>
>> Is this already possible?
>
> Hi Arnaldo,
>
> for me this works in 3.19.0. I'm using the attached script to help me add
> probes to /sys/kernel/debug/tracing/uprobe_events which I can then see with
> 'sudo perf list' and use from the other perf subcommands. Tracing arguments is
> also working fine:
Yeah, perf probe should be able to do the same thing without debuginfo.
If not, there must be a bug. :(
>
> --- snip ---
> $ uprobe /lib/x86_64-linux-gnu/libc.so.6 malloc %di
> $ sudo perf stat -e uprobes:* ls
> ...
> Performance counter stats for 'ls':
> ...
> 218 uprobes:malloc_1
> $ sudo perf record -euprobes:malloc_1 ls >/dev/null 2>&1
> $ sudo perf script
> ls 21084 [003] 10825.526815: uprobes:malloc_1: (7f772bfc2700) arg1=0x238
> ls 21084 [003] 10825.526917: uprobes:malloc_1: (7f772bfc2700) arg1=0x238
> ls 21084 [003] 10825.526968: uprobes:malloc_1: (7f772bfc2700) arg1=0x78
> ls 21084 [003] 10825.527089: uprobes:malloc_1: (7f772bfc2700) arg1=0x5
> ls 21084 [003] 10825.527132: uprobes:malloc_1: (7f772bfc2700) arg1=0x78
> ...
> --- snip ---
>
> This is superuseful to me, so thank you all for working on perf!
>
> I failed to manage placing proper probes in C++-Code with perf probe, so I
> hacked the script together after reading Brendans ftrace article on LWN.
Hmm, that must be a bug, so it should be fixed.
Thank you!
--
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-06-30 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 19:06 perf probe an addr without debuginfo Brendan Gregg
2015-06-28 15:46 ` Benjamin King
2015-06-29 15:00 ` Arnaldo Carvalho de Melo
2015-06-30 6:44 ` Benjamin King
2015-06-30 8:51 ` Masami Hiramatsu [this message]
2015-06-30 18:07 ` Brendan Gregg
2015-06-30 20:44 ` Benjamin King
2015-06-30 7:37 ` Masami Hiramatsu
2015-06-30 18:40 ` Brendan Gregg
2015-07-01 11:05 ` Masami Hiramatsu
2015-07-06 23:18 ` Brendan Gregg
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=559258A4.2020205@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=acme@kernel.org \
--cc=benjaminking@web.de \
--cc=brendan.d.gregg@gmail.com \
--cc=cti.systems-productivity-manager.ts@hitachi.com \
--cc=linux-perf-users@vger.kernel.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.