linux-kernel - Re: [RFC PATCH] tsc: synchronize TSCs on buggy Intel Xeon E5 CPUs with offset error

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]

Date:	Fri, 13 Nov 2015 13:13:29 -0800
From:	Dave Hansen <dave.hansen@...el.com>
To:	Peter Zijlstra <peterz@...radead.org>, gratian.crisan@...com
Cc:	Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...hat.com>,
	"H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	Borislav Petkov <bp@...en8.de>, Josh Cartwright <joshc@...com>,
	gratian@...il.com
Subject: Re: [RFC PATCH] tsc: synchronize TSCs on buggy Intel Xeon E5 CPUs
 with offset error

On 11/09/2015 02:02 PM, Peter Zijlstra wrote:
> On Mon, Nov 09, 2015 at 01:59:02PM -0600, gratian.crisan@...com wrote:
>> The Intel Xeon E5 processor family suffers from errata[1] BT81:
> 
>> +#ifdef CONFIG_X86_TSC
>> +	/*
>> +	 * Xeon E5 BT81 errata: TSC is not affected by warm reset.
>> +	 * The TSC registers for CPUs other than CPU0 are not cleared by a warm
>> +	 * reset resulting in a constant offset error.
>> +	 */
>> +	if ((c->x86 == 6) && (c->x86_model == 0x3f))
>> +		set_cpu_bug(c, X86_BUG_TSC_OFFSET);
>> +#endif
> 
> That's hardly a family, that's just one, Haswell server.

How did you come up with that x86_model?  The document you linked to
claimes that "Extended Model" is 0010b and "Model Number" is 1101b, so
the x86_model you are looking for should be 0x2d.

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