On Tue, Sep 23, 2008 at 4:32 PM, Klaus Egbers <[EMAIL PROTECTED]> wrote: >> > How do convince pfmon to report the number of retired instructions for >> each call (using --trigger-code-repeat)? >> >> You mean aggregate over all calls? If so, then yes, use >> --trigger-code-repeat. > > No. I do not want to aggregate. I want to count the retired instructions for > each call. So one sample for each start/stop iteration. Is it possible?
Ok, if you are using --follow-pthread, then it should print total count per thread at the end. The only things it won't give you is the number of calls/threads. > > Here is want I want to do :-) > I want to know how many instructions were retired for every single > pthread_mutex_lock. This allows me to measure the contention between multiple > threads. > Yes, I figured you were after something like that, spinning will increase count of instructions_retired ;-> ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
