linux-kernel - Re: RFC: Bogus setting of CONSTANT TSC ?

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]

Date:	Sun, 13 Mar 2011 18:06:32 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Dave Jones <davej@...hat.com>, x86@...nel.org,
	Andi Kleen <andi@...stfloor.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: RFC: Bogus setting of CONSTANT TSC ?

> This was initially introduced with commit 39b3a7 ([PATCH] i386/x86-64:
> Generalize X86_FEATURE_CONSTANT_TSC flag), though the changelog is
> utterly useless. Andi ??

Only Nehalem and beyond set the 8000_0007 flag, but Intel has had a constant
TSC since Yonah. That is what this logic implements.

However on Nehalem and beyond if the 8000_0007 is clear the BIOS wants
to tell us that it knows the system doesn't have a synchronized TSC.
This is currently still broken, but the timer watchdog usually catches
it later. It only affects a few relatively obscure systems.

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