Re: CALatencyLog?
Re: CALatencyLog?
- Subject: Re: CALatencyLog?
- From: "B.J. Buchalter" <email@hidden>
- Date: Tue, 14 Sep 2010 19:07:53 -0400
On Sep 14, 2010, at 7:02 PM, Jeff Moore wrote:
> The latency log code was a hack up we did based on the latency tool from the system_cmds project in Darwin. We removed it mostly because we hadn't been maintaining it as well as we should have after we started using dtrace to look at most performance issues.
>
> You may be able to recreate what you need with the old version of the CALatencyLog code you have and crossing it with a current version latency tool code in the current version of the system_cmds project.
Well, maybe dtrace would be better than going down that road.
The issue is that AFAIKT, dtrace does not "see" KEXTs. I need to instrument some stuff in my driver and pull it out. I have been using the chud signposts and doing a system trace in Shark (and the latency code also sees the kdebug entries that shark sees), but it is very difficult to interpret and visualize the things I am looking at with shark). Is there a way to get dtrace to trigger on and capture stuff that I am logging through the kdebug mechanism, thus allowing me to add visibility to the kext?
Thanks!
Best regards,
B.J. Buchalter
Metric Halo
http://www.mhlabs.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden