On 11/18/08 12:30, Raj, Ashok wrote:
>
>> -----Original Message-----
>> From: Eric.Saxe at Sun.COM [mailto:Eric.Saxe at Sun.COM]
>> Sent: Tuesday, November 18, 2008 11:54 AM
>> To: Bill.Holler at Sun.COM
>> Cc: Raj, Ashok; Randall Fishel; tesla-dev at opensolaris.org
>> Subject: Re: [tesla-dev] Request for comment for PSARC onapager about CPU
>> idle nofication interface
>>
>> Bill Holler wrote:
>>
>>> What interface should we use if things like intr rate and previous
>>> idle duration are canlculated in the kernel? Should this be an
>>> argument to the idle callback? Another option is to keep this data
>>> in the per-cpu mach_cpu structure which the callbacks can access.
>>>
>>>
>> It would probably be better provide this through accessor interfaces...
>> rather than having the callbacks have to know about mach_cpu...
>>
>
>
> Much better!
What data do we want in these accessor interfaces?
This data is available:
1) max-idle duration via LAPIC Current Count register.
2) last idle duration
3) possibly a running average idle time
4) ACPI round trip latency of the current target C-State.
5) intr rate calculation.
6) target C-State.
Is there anything else?
Which of this data is useful?
Bill