Interesting. I don't see a description of how the counters can be linked together in this new version.
I'm still wondering about the multiplexing capability (he calls it scheduling)... how do you related a cycles count to each set for scaling purposes? How do you know what is in each set? Regards, - Corey Corey Ashford Software Engineer IBM Linux Technology Center, Linux Toolchain Beaverton, OR 503-578-3507 cjash...@us.ibm.com "stephane eranian" <eran...@googlemail.com> wrote on 12/11/2008 08:05:07 AM: [snip] > This is v3 of our performance counters subsystem implementation. It can > be accessed at: > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git > perfcounters/core > > (or via http://people.redhat.com/mingo/tip.git/README ) > > We've made a number of bigger enhancements in the -v3 release: > > - The introduction of new "software" performance counters: > PERF_COUNTER_CPU_CLOCK and PERF_COUNTER_TASK_CLOCK. (With page-fault, > context-switches and block-read event counters planned as well) > > These sw-counters, besides being useful to applications and being nice > generalizations of the performance counter concept, are also helpful > in porting performance counters to new architectures: the software > counters will work fine without any PMU. Applications can thus > standardize on the availability of _some_ performance counters on all > Linux systems all the time, regardless of current PMU support status. > > - The introduction of counter groups: counters can now be grouped up > when created. Such counter groups are scheduled atomically and can > have their events taken with precise (and atomic) multi-dimensional > timestamps as well. > > The counter groups are a natural extension of the current single > counters, they still act as individual counters as well. > > [ It's a bit like task or tty groups - losely coupled counters with a > strong self-identity. The grouping can be arbitrary - there can be > multiple counter groups per task - mixed with single counters as > well. The concept works for CPU/systemwide counters as well. ] > > - The addition of a lowlevel counter hw driver framework that allows > assymetric counter implementation. The sw counters now use this > facility. > > - The ability to turn all counters of a task on/off via a single system > call. > > - The syscall API has been streamlined significantly - see further below > for details. The event type has been widened to 64 bits for powerpc's > needs, and a few reserve bits have been introduced. > > - The ability to turn all counters of a task on/off via a single system > call. This is eseful to applications that self-profile and/or want to > do runtime filtering of which functions to profile. (there's also a > "hw_event.disabled" bit in the API to create counters in disabled > state straight away - useful to powerpc for example - this code is not > fully complete yet. It's the next entry on our TODO list :-) > > - [ lots of other updates, fixes and cleanups. ] > [snip] ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ perfmon2-devel mailing list perfmon2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
