Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: AMD X2 unsynced TSC fix?
Date: Mon, 30 Oct 2006 11:22:45 -0600
Message-ID: <1449F58C868D8D4E9C72945771150BDF153775@SAUSEXMB1.amd.com>
In-Reply-To: <1162058915.14733.2.camel@mindpipe>
Thread-Topic: AMD X2 unsynced TSC fix?
Thread-Index: Acb6vCNI2iQIilqMRjmEnvBD8ZrqYwBi3aiQ
From: "Langsdorf, Mark" <mark.langsdorf@amd.com>
To: "Lee Revell" <rlrevell@joe-job.com>
cc: linux-kernel@vger.kernel.org
Content-Type: text/plain;
 charset=us-ascii
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1217
Lines: 33

> > Agreed, I had to turn about 20 dual-core servers to single 
> > core because the only way to get a monotonic gtod made it
> > so slow that it was not worth using a dual-core. I initially
> > considered buying one dual-core AMD for my own use, but after
> > seeing this, I'm definitely sure I won't ever buy one as
> > long as this problem is not fixed, as it causes too
> > many problems.
> 
> Does anyone know if the problem will really be fixed in new 
> CPUs, as AMD promised a year or so ago?
> 
> http://lkml.org/lkml/2005/11/4/173
> 
> Since that post, there has been Socket F and AM2 which apparently have
> the same issue. 
> Were the AMD guys just blowing smoke?

AMD was not blowing smoke.  Future AMD processors will have 
pstate/cstate invariant TSCs detectable by a CPUID bit.

Unfortunately, those processors have not be released yet, and
I can't comment on their release timeframe, other than to say
they are on our roadmap.

-Mark Langsdorf
AMD, Inc.


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