From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-kernel@vger.kernel.org, acme@kernel.org,
peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com,
masami.hiramatsu.pt@hitachi.com, wangnan0@huawei.com,
namhyung@kernel.org, srikar@linux.vnet.ibm.com,
naveen.n.rao@linux.vnet.ibm.com
Subject: Re: [RFC] perf probe: Fix module probe issue if no dwarf support
Date: Tue, 26 Apr 2016 14:34:40 +0530 [thread overview]
Message-ID: <571F2F28.50000@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160426062925.9dbfda280af62f077a27e297@kernel.org>
On Tuesday 26 April 2016 02:59 AM, Masami Hiramatsu wrote:
> On Mon, 25 Apr 2016 16:08:28 +0530
> Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com> wrote:
>
>> Perf is not able to register probe in kernel module when dwarf supprt
>> is not there(and so it goes for symtab). Perf passes full path of
>> module where only module name is required which is causing the problem.
>> This patch fixes this issue.
>>
>> Before applying patch:
>>
>> $ dpkg -s libdw-dev
>> dpkg-query: package 'libdw-dev' is not installed ...
>>
>> $ ./perf probe -m /linux/samples/kobject/kobject-example.ko foo_show
>> Added new event:
>> probe:foo_show (on foo_show in /linux/samples/kobject/kobject-example.ko)
>>
>> You can now use it in all perf tools, such as:
>>
>> perf record -e probe:foo_show -aR sleep 1
>>
>> $ cat /sys/kernel/debug/tracing/kprobe_events
>> p:probe/foo_show /linux/samples/kobject/kobject-example.ko:foo_show
>>
>> After applying patch:
>>
>> $ ./perf probe -m /linux/samples/kobject/kobject-example.ko foo_show
>> Added new event:
>> probe:foo_show (on foo_show in kobject_example)
>>
>> You can now use it in all perf tools, such as:
>>
>> perf record -e probe:foo_show -aR sleep 1
>>
>> $ cat /sys/kernel/debug/tracing/kprobe_events
>> p:probe/foo_show kobject_example:foo_show
>>
> Looks good to me :)
> However, it seems that this patch depends on your previous patch
> ("perf probe: Fix offline module name missmatch issue")
> In that case, could you make these a series of patches?
>
> Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Thanks Masami,
I've sent v2 with changes you suggested. Please review it.
Regards,
Ravi
next prev parent reply other threads:[~2016-04-26 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 10:38 [RFC] perf probe: Fix offline module name missmatch issue Ravi Bangoria
2016-04-25 10:38 ` [RFC] perf probe: Fix module probe issue if no dwarf support Ravi Bangoria
2016-04-25 21:29 ` Masami Hiramatsu
2016-04-26 9:04 ` Ravi Bangoria [this message]
2016-04-25 21:24 ` [RFC] perf probe: Fix offline module name missmatch issue Masami Hiramatsu
2016-04-26 2:19 ` Masami Hiramatsu
2016-04-26 9:00 ` Ravi Bangoria
2016-04-26 8:56 ` Ravi Bangoria
2016-04-26 9:15 ` Wangnan (F)
2016-04-26 10:45 ` Ravi Bangoria
2016-04-26 10:46 ` Masami Hiramatsu
2016-04-26 14:29 ` Ravi Bangoria
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=571F2F28.50000@linux.vnet.ibm.com \
--to=ravi.bangoria@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).