Klaus, On Tue, Sep 23, 2008 at 5:43 PM, Klaus Egbers <[EMAIL PROTECTED]> wrote: >> 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. > > I need the values for each call. Therefore, I added > read_incremental_results(sdesc); > show_incr_results(sdesc, 0); > to task_handle_stop_trigger in pfmon_task.c > On the first glance this seems to do what I want. Any objections? :-) Did I > miss anything? > If that works for you, I am fine with it. You can modify your copy of pfmon anyway you like.
Your example leads me to believe that it would be nice if pfmon would at least report the number of time the start and stop triggers have been hit for each perfmon context. ------------------------------------------------------------------------- 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
