linux-kernel - Re: [patch-mm 00/25] High resolution timer updates and x86_64 support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1182217979.3014.3.camel@laptopd505.fenrus.org>
Date:	Mon, 18 Jun 2007 18:52:58 -0700
From:	Arjan van de Ven <arjan@...radead.org>
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>,
	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>
Subject: Re: [patch-mm 00/25] High resolution timer updates and x86_64
	support - V2

On Mon, 2007-06-18 at 16:06 -0400, Valdis.Kletnieks@...edu wrote:
> 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:


looks like something broke the /proc/acpi/processor/*/power file
data....

can you check in that file to see if there is actual C-state time
accounting going on?
(it is in mainline, so if it's not then it's an -mm or -hrt bug)

-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

-
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/