lkml.org 
[lkml]   [2006]   [Oct]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRE: AMD X2 unsynced TSC fix?
Date
From
> > 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/

\
 
 \ /
  Last update: 2006-10-30 18:37    [W:0.154 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site