linux-kernel - Re: [patch 13/19] GTOD: Mark TSC unusable for highres timers

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: <20061110131248.GA27251@elte.hu>
Date:	Fri, 10 Nov 2006 14:12:48 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Andi Kleen <ak@...e.de>
Cc:	Pavel Machek <pavel@....cz>, Andrew Morton <akpm@...l.org>,
	tglx@...utronix.de, john stultz <johnstul@...ibm.com>,
	LKML <linux-kernel@...r.kernel.org>, Len Brown <lenb@...nel.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Roman Zippel <zippel@...ux-m68k.org>
Subject: Re: [patch 13/19] GTOD: Mark TSC unusable for highres timers


* Andi Kleen <ak@...e.de> wrote:

> > we could, but it would have to be almost empty right now :-) Reason: 
> > even on systems that have (hardware-initialized) 'perfect' TSCs and 
> > which do not support any frequency scaling or power-saving mode, our 
> > current TSC initialization on SMP systems introduces a small (1-2 usecs) 
> > skew.
> 
> On Intel we don't sync the TSC anymore [...]

yeah, after i reported this a few months ago ;-)

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