Subject: Re: [patch] Mark rdtsc as sync only for netburst, not for core2
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org, akpm@osdl.org
In-Reply-To: <456D4648.7000509@linux.intel.com>
References: <1164709708.3276.72.camel@laptopd505.fenrus.org>
	 <200611281136.29066.ak@suse.de> <1164774239.15257.5.camel@ymzhang>
	 <456D372C.9080800@linux.intel.com> <1164787104.2899.7.camel@ymzhang>
	 <456D4648.7000509@linux.intel.com>
Content-Type: text/plain
Date: Wed, 29 Nov 2006 17:07:48 +0800
Message-Id: <1164791268.2873.5.camel@ymzhang>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 846
Lines: 23

On Wed, 2006-11-29 at 09:35 +0100, Arjan van de Ven wrote:
> 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...
Thanks.

> (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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/