linux-kernel - Re: [patch] Mark rdtsc as sync only for netburst, not for core2

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

Date:	Wed, 29 Nov 2006 09:35:20 +0100
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
CC:	Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org,
	akpm@...l.org
Subject: Re: [patch] Mark rdtsc as sync only for netburst, not for core2

Zhang, Yanmin wrote:
>> but second of all, the core2 cpus are dual core so.. .what does it 
>> bring you at all?
> 
> When there is only one cpu (or UP), the go backwards issue doesn't exist,

it does exist for single-socket dual core already. And core2 is dual 
core...

> so
> don't use cpuid here for UP. Another function init_amd already does so.
> 
not anymore.. that got fixed very recently...
(but you are right; on AMD the speculation is even bigger so there 
even on single core you need cpuid)
-
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/