On 01/20/2015 09:08 AM, AKel wrote:
Hi,
I'm trying to profile an application which is spending quite a bit of time
in the kernel (~40% in do_raw_spin_lock for example). To fully understand
what is happening I would like to generate a call stack using perf (or
otherwise) to see where the calls to this function are originating from.
Is this possible? My hands are slightly tied in that I don't have sudo
access to the system I'm working on, so a solution which accounts for this
would be greatly appreciated. Even transferring files to/from the system
is very difficult so I'm rather restricted in what i can do.
I suspect you will have to resolve the sudo issue by getting sudo.
Ignoring that for the time-being, it sounds like you could use the
call-graph functionality of perf record/report/top?
rick jones
--
To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
