At 1:29 PM -0400 6/21/02, Jim Magee wrote: No real-time notifications. But there is a trace mechanism that gives you the raw information to post-process. That's the same data that feeds the sc_usage, fs_usage, and latency performance utility tools. Looking at the man page for sc_usage gave me another idea. I saw the CPU_TIME, WAIT_TIME, and CUR_WAIT_TIME column headers. If the active (function) profiler code on the user side had fast read access to such information at the thread level, and if the resolution of that information was at RTC register granularity, then I think the in/out time differentials could be calculated. All without having to mess with any callbacks/signals etc. Where would I look for more information on the thread specific cpu accounting information? -- Jonathan Hess ViviStar Consulting http://www.vivistar.com/ mailto:jahess@vivistar dot com _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.