[tesla-dev] [powertop bug] c-state kstat ?
Aubrey Li
aubrey at blastwave.org
Wed May 21 17:45:56 PDT 2008
On Thu, May 22, 2008 at 2:35 AM, Bill Holler <Bill.Holler at sun.com> wrote:
> What are the thoughts on integrating a c-state kstat into Nevada?
> We do not currently support c-states and may never support
> c-states on some platforms. Would it cause user confusion if
> we report an unsupported feature?
>
I think we are talking about idle state here.
there is a kstat member "supported_max_cstates".
At least we support C0 and C1, on all platform.
So if deeper c-states is not supported,
supported_max_cstates = 1, here, forever.
this info is enough for powertop.
Thanks.
-Aubrey
>
> Darrin Johnson wrote:
>>
>> I would save shelve the issue until ktstat c-state info is there. The
>> whitespace is fine for now.
>>
>> Darrin
>>
>> Aubrey Li wrote:
>>
>>>
>>> On Wed, May 21, 2008 at 11:19 PM, Rafael Vanoni <Rafael.Vanoni at sun.com>
>>> wrote:
>>>
>>>>
>>>> But we're still only reporting C-states that the processor transitions
>>>> to.
>>>> If the system supports Cn, we only report it's existence after the first
>>>> transition to it. If this is the desired behavior, we gotta update the
>>>> manual.
>>>>
>>>>
>>>
>>> well, you're right, this may not the desired behavior but it's the
>>> current
>>> behavior. So i guess as for window position, if we need to fix this bug
>>> right now, this is the best way so far.
>>> We can change this after kstat c-state info get supported.
>>>
>>> What do you think?
>>>
>>> Thanks,
>>> -Aubrey
>>> _______________________________________________
>>> tesla-dev mailing list
>>> tesla-dev at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/tesla-dev
>>>
>>
>>
>
>
More information about the tesla-dev
mailing list