[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <653FFBB4508B9042B5D43DC9E18836F5010913F8@scsmsx415.amr.corp.intel.com>
Date: Mon, 18 Jun 2007 15:10:45 -0700
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To: <Valdis.Kletnieks@...edu>
Cc: "Thomas Gleixner" <tglx@...utronix.de>,
"LKML" <linux-kernel@...r.kernel.org>,
"Andrew Morton" <akpm@...l.org>, "Ingo Molnar" <mingo@...e.hu>,
"Andi Kleen" <ak@...e.de>, "Chris Wright" <chrisw@...s-sol.org>,
"Arjan van de Ven" <arjan@...radead.org>
Subject: RE: [patch-mm 00/25] High resolution timer updates and x86_64 support - V2
>-----Original Message-----
>From: Valdis.Kletnieks@...edu [mailto:Valdis.Kletnieks@...edu]
>Sent: Monday, June 18, 2007 2:50 PM
>To: Pallipadi, Venkatesh
>Cc: Thomas Gleixner; LKML; Andrew Morton; Ingo Molnar; Andi
>Kleen; Chris Wright; Arjan van de Ven
>Subject: Re: [patch-mm 00/25] High resolution timer updates
>and x86_64 support - V2
>
>On Mon, 18 Jun 2007 13:24:33 PDT, "Pallipadi, Venkatesh" said:
>
>> >state2/time: -159524787
>> >state2/usage: 15007443
>> >
>>
>> The problem is powertop only understands
>/proc/acpi/processor/CPU*/power
>> for
>> and not /sys..cpuidle for the moment.
>>
>> I had a patch in recent cpuidle fixes series that makes
>/proc interface
>> active
>> again with cpuidle which should correct this. Those patches
>are not in
>> rc4-mm2-hrt4, but are there in latest rc4-hrt and rc5-hrt series.
>
>OK, so I've got a 32/64 bug that isn't the cause of *this*
>issue because
>powertop isn't looking at the broken value.
>
Yes. The output does indicate a bug in cpuidle /sysfs part. Will look at
sysfs output of cpuidle and fix those issues soon.
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