[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <924EFEDD5F540B4284297C4DC59F3DEEC83EF5@orsmsx423.amr.corp.intel.com>
Date: Fri, 28 Mar 2008 16:51:57 -0700
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To: "David Brownell" <david-b@...bell.net>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
<linux-kernel@...r.kernel.org>, "Rafael J. Wysocki" <rjw@...k.pl>,
<linux-acpi@...r.kernel.org>, "Len Brown" <lenb@...nel.org>
Subject: RE: 2.6.25 regression: powertop says 120K wakeups/sec
>-----Original Message-----
>From: David Brownell [mailto:david-b@...bell.net]
>Sent: Friday, March 28, 2008 4:36 PM
>To: Pallipadi, Venkatesh
>Cc: Andrew Morton; linux-kernel@...r.kernel.org; Rafael J.
>Wysocki; linux-acpi@...r.kernel.org; Len Brown
>Subject: Re: 2.6.25 regression: powertop says 120K wakeups/sec
>
>On Friday 28 March 2008, Venki Pallipadi wrote:
>
>> I think I figured out the bug...
>>
>> Can you try the below patch and confirm that it works (over
>upstream - ignore
>> the earlier revert patch I sent to you).
>
>That seems to do the job ... thanks! One more regression
>fixed, it feels like RC7 is almost done. :)
>
>It still says odd things about C0 vs C1 though: powertop
>says 100% of the time is in C0, but this patch would seem
>to be irrelevant if that were true.
>
Great!
100% C0 is not real reading. The problem behind that is there is no wat
to measure exact C1 idle time with halt based C1s. So, we always used to
report 0 time in acpi and that's what is reported by powertop.
This should be fixed in future, as we now export approx time (even
though not exact) in cpuidle and powertop is about to start using it.
Thanks,
Venki
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists