From: Peter Zijlstra <peterz@infradead.org>
To: john smith <whalajam@yahoo.com>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: perf report for .ko files
Date: Tue, 26 Jan 2010 20:21:55 +0100 [thread overview]
Message-ID: <1264533715.4283.1961.camel@laptop> (raw)
In-Reply-To: <666103.59126.qm@web55005.mail.re4.yahoo.com>
On Mon, 2010-01-25 at 16:34 -0800, john smith wrote:
> How can "perf report" be used to get info on (only) the specific manually loadable modules?
> Driver entry points are reported but without full breakdown (on all the calls).
Since its sampling it could be a function is just not hit, another
possibility is inlining of functions, we simply cannot see inlined
functions.
> If "--symbols" option is used, most of the symbols are not found.
> ("--dsos" doesn't seem to help)
I'm not a big module user, but I think --dsos should work, if not feel
free to send a patch to rectify this situation.
--dsos does appear to work on my laptop (where I have iwlagn as a module
since it sometimes needs a reload to start working, which is hard when
build in).
perf report --dsos "[iwlagn]"
does indeed give me all iwlagn hits, albeit without symbol information,
not sure why that is, /proc/kallsyms does seem to include some iwlagn
symbols.
Arnaldo might have a clue.
next prev parent reply other threads:[~2010-01-26 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 0:34 perf report for .ko files john smith
2010-01-26 19:21 ` Peter Zijlstra [this message]
2010-01-26 21:05 ` Arnaldo Carvalho de Melo
2010-01-29 18:55 ` john smith
2010-01-29 19:15 ` Arnaldo Carvalho de Melo
2010-01-29 21:59 ` john smith
2010-01-30 6:45 ` Mike Galbraith
2010-02-03 17:28 ` 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=1264533715.4283.1961.camel@laptop \
--to=peterz@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=whalajam@yahoo.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