Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

IO Cycle Telemetry Window

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

IO Cycle Telemetry Window

Subject: IO Cycle Telemetry Window
From: Stéphane Letz <email@hidden>
Date: Wed, 31 Aug 2005 10:03:00 +0200


>After building HALLab, you choose the "IO Cycle Telemetry Window"
>item from the "New" menu in the "File menu". This brings up the
>window that provides the UI on the telemetry client. Note that the
>process needs to be run as root to use the latency tracing facilities.

>I should also point out that the source code for the telemetry client
>engine is in our SDK's PublicUtility directory. It is self contained
>so you can drop it into your own test tools as well.

>I'm happy to help you puzzle through the telemetry data.

Concerning the "IO Cycle Telemetry Window", I tried to measure what happens when an application is used with our used-land driver (launching iTunes running with our driver running as the default system driver) but i don't see any data printed in the IO Cycle Telemetry Window. It works with Built-in or any aggregate device I also have.

I see a "CAHALIOCycleTelemetryClient::Update: no port" message displayed by HALLab. Is there anything special to implement in the user-land device so that it can be measured?

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


Follow-Ups:

Re: IO Cycle Telemetry Window
From: Jeff Moore <email@hidden>


Prev by Date:
has this been done?

Next by Date:
lightweight traces in kernelmode?

Previous by thread:
has this been done?

Next by thread:
Re: IO Cycle Telemetry Window

Index(es):

Date
Thread