From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jerome Correnoz <jerome.correnoz@st.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Is it possible to get source code annotation for kernel modules ?
Date: Tue, 16 Dec 2014 08:44:32 -0300 [thread overview]
Message-ID: <20141216114432.GQ9845@kernel.org> (raw)
In-Reply-To: <loom.20141215T094546-812@post.gmane.org>
Em Mon, Dec 15, 2014 at 08:51:36AM +0000, Jerome Correnoz escreveu:
> Hi,
>
> Could someone please provide support on it ?
>
> We would like to know if 'perf annotate' can allow to display the C source
> code interleaved with disassembly for the kernel modules (we can get it only
> for user space application. For kerne modules, we only have the
> disassembly). Is it feasible for kernel modules ?
Yes it is possible, as is possible for userspace, someone has to work on it.
- Arnaldo
next prev parent reply other threads:[~2014-12-16 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 21:05 Is it possible to get source code annotation for kernel modules ? Jerome Correnoz
2014-12-15 8:51 ` Jerome Correnoz
2014-12-16 11:44 ` Arnaldo Carvalho de Melo [this message]
2014-12-18 15:23 ` Jerome CORRENOZ
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=20141216114432.GQ9845@kernel.org \
--to=acme@kernel.org \
--cc=jerome.correnoz@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox