linux-kernel - Re: [PATCH] Skip tsc synchronization checks if CONSTANT

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 22 Oct 2008 21:26:22 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Alok Kataria <akataria@...are.com>
Cc:	Andi Kleen <andi@...stfloor.org>, "H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Daniel Hecht <dhecht@...are.com>
Subject: Re: [PATCH] Skip tsc synchronization checks if CONSTANT_TSC bit is
	set.


* Alok Kataria <akataria@...are.com> wrote:

> Skip tsc synchronization checks if CONSTANT_TSC bit is set.
> 
> From: Alok N Kataria <akataria@...are.com>
> 
> TSC synchronization checks between CPU's bail out even if we see a 
> distortion of a single cycle. This makes the TSC mostly unsuable in a 
> virtualized environment.
> 
> The CONSTANT_TSC bit tells us if the hardware exports a constant TSC, 
> we can use this bit to trust the hardware and skip the TSC sync checks 
> at bootup.

the sync check is there to check the _offset_ between CPUs. CONSTANT_TSC 
is not a guarantee that the TSC will be coherent across all CPUs.

so this patch is fundamentally wrong.

	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/