Tracing latencies
Tracing latencies
- Subject: Tracing latencies
- From: Stéphane Letz <email@hidden>
- Date: Tue, 15 Nov 2005 17:08:19 +0100
Hi,
I'm trying to use latency tracing tools to understand what happens in
a IO proc running at 64 frames on a recent Powerbook 64 (OSX 10.4.3)
that shows constant kAudioDeviceProcessorOverload.
I'm using latency.c and CALatencyLog code (starting from the
AUTracer.cpp file) to trigger latency capture when an
kAudioDeviceProcessorOverload notification is received.
I get this kind if file and I'm wondering why iI see a policy =
TIMESHARE type of thread when a was expecting tracing the real-time
IO thread.
Captured Latency Log for I/O Cycle Overload
------------------------------------------------------------------------
-----------------------------------------------------
Thu Jan 1 01:00:00 scheduling latency = 9001.2us
sleep_request = 1000us policy = TIMESHARE priority = default
RelTime(Us) Delta debugid
arg1 arg2 arg3 arg4 thread cpu command
862.0 0.0 MACH_MKRUNNABLE 1e4d318
5e 0 0 2306000 0 jackdmp
875.8 13.8 MACH_SCHED jackdmp @ pri 27 -->
kernel_task @ pri 94K 2306000 0
883.8 7.9 MACH_CALLOUT 143f38
0 0 0 1e4d318 0 kernel_task
892.0 8.2 MACH_SCHED kernel_task @ pri 94 --
> jackdmp @ pri 27* 1e4d318 0
907.6 15.6 MACH_MKRUNNABLE 1732000
51 0 0 2306000 0 jackdmp
then I don't think the result can be analysed because I don't see the
RT thread in the trace.
How the latency tools must be configurated ?
Thanks
Stephane Letz
_______________________________________________
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