[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <653FFBB4508B9042B5D43DC9E18836F501091308@scsmsx415.amr.corp.intel.com>
Date: Mon, 18 Jun 2007 13:24:33 -0700
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To: <Valdis.Kletnieks@...edu>, "Thomas Gleixner" <tglx@...utronix.de>
Cc: "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 1:07 PM
>To: Thomas Gleixner
>Cc: LKML; Andrew Morton; Ingo Molnar; Andi Kleen; Chris
>Wright; Arjan van de Ven; Pallipadi, Venkatesh
>Subject: Re: [patch-mm 00/25] High resolution timer updates
>and x86_64 support - V2
>
>On Sat, 16 Jun 2007 10:36:00 -0000, Thomas Gleixner said:
>> The following patch series contains:
>>
>> - dyntick bugfixes for -mm (caused by the cpuidle changes in ACPI)
>>
>> - updates and improvements to high resolution timer / dynticks
>>
>> - high resolution timer / dynticks support for x86_64
>
>Am running with the 22-rc4-mm2-hrt4 patch on my Latitude D820.
> Mostly seems
>to work, but for some reason the Intel 'powertop' util thinks
>it's 100% busy:
>
> PowerTOP version 1.7 (C) 2007 Intel Corporation
>
>Cn Avg residency (5s) P-states (frequencies)
>C0 (cpu running) (100.0%)
>C1 0.0ms ( 0.0%) 2.00 Ghz 0.0%
>C2 0.0ms ( 0.0%) 1.67 Ghz 0.0%
>C3 0.0ms ( 0.0%) 1333 Mhz 0.0%
> 1000 Mhz 100.0%
>
>In reality:
>
>[/sys/devices/system/cpu/cpu0/cpuidle] for i in */*; do echo
>-n "$i: "; cat $i; done
>state0/latency: 1
>state0/power: 1000
>state0/time: 0
>state0/usage: 3
>state1/latency: 1
>state1/power: 500
>state1/time: 1756017623
>state1/usage: 1837402
>state2/latency: 57
>state2/power: 100
>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.
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