Subject: Re: perf report for .ko files
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>
In-Reply-To: <666103.59126.qm@web55005.mail.re4.yahoo.com>
References: <666103.59126.qm@web55005.mail.re4.yahoo.com>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 26 Jan 2010 20:21:55 +0100
Message-ID: <1264533715.4283.1961.camel@laptop>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1211
Lines: 31

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/