linux-kernel - Re: [patch 00/22] high resolution timers / dynamic ticks

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] [day] [month] [year] [list]

Message-Id: <200610161253.49969.ak@suse.de>
Date:	Mon, 16 Oct 2006 12:53:49 +0200
From:	Andi Kleen <ak@...e.de>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	John Stultz <johnstul@...ibm.com>,
	Valdis Kletnieks <valdis.kletnieks@...edu>,
	Dave Jones <davej@...hat.com>,
	David Woodhouse <dwmw2@...radead.org>,
	Jim Gettys <jg@...top.org>,
	Roman Zippel <zippel@...ux-m68k.org>, akpm@...l.org
Subject: Re: [patch 00/22] high resolution timers / dynamic ticks - V3

On Friday 06 October 2006 09:28, Arjan van de Ven wrote:
> 
> > But usually the problem wasn't that it was too slow, but that
> > it completely stopped in C2 or deeper. I don't think there
> > is a way to work around that except for not using C2 or deeper
> > (not an option) or using a different timer source.
> 
> actually it's supposed to be C3 where lapic stops, not C2.

I've seen systems where it stopped in C2. The BIOS often 
mix these states up anyways and report C3 as a kind of C2
(with the cache flushing etc in SMM) and the other way round.
I think that's related to getting better performance on
Windows.

-Andi

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