From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
mhiramat@kernel.org, wangnan0@huawei.com, namhyung@kernel.org,
srikar@linux.vnet.ibm.com, naveen.n.rao@linux.vnet.ibm.com
Subject: Re: [PATCH 1/2] perf probe: Fix module probe issue if no dwarf support
Date: Tue, 26 Apr 2016 20:42:46 +0530 [thread overview]
Message-ID: <571F856E.80904@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160426143453.GD11033@kernel.org>
On Tuesday 26 April 2016 08:04 PM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Apr 26, 2016 at 07:55:40PM +0530, Ravi Bangoria escreveu:
>> 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.
> Is this v3? What has changed from v2?
>
> - Arnaldo
Yes Arnaldo. But I changed it from [RFC] to [PATCH], so didn't include
version. Here is [RFC v2] link: https://lkml.org/lkml/2016/4/26/114
Changes w.r.t. [RFC v2]:
- Swapped patch in series and move definition of find_module_name in
other patch.
Regards,
Ravi
next prev parent reply other threads:[~2016-04-26 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 14:25 [PATCH 1/2] perf probe: Fix module probe issue if no dwarf support Ravi Bangoria
2016-04-26 14:25 ` [PATCH 2/2] perf probe: Fix offline module name missmatch issue Ravi Bangoria
2016-04-26 14:45 ` Masami Hiramatsu
2016-04-27 15:38 ` [tip:perf/core] " tip-bot for Ravi Bangoria
2016-04-26 14:34 ` [PATCH 1/2] perf probe: Fix module probe issue if no dwarf support Arnaldo Carvalho de Melo
2016-04-26 15:12 ` Ravi Bangoria [this message]
2016-04-26 15:44 ` Arnaldo Carvalho de Melo
2016-04-26 14:45 ` Masami Hiramatsu
2016-04-26 15:49 ` Arnaldo Carvalho de Melo
2016-04-27 15:38 ` [tip:perf/core] " tip-bot for 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=571F856E.80904@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=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