linux-kernel - RE: AMD X2 unsynced TSC fix?

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]

Message-ID: <1449F58C868D8D4E9C72945771150BDF153775@SAUSEXMB1.amd.com>
Date:	Mon, 30 Oct 2006 11:22:45 -0600
From:	"Langsdorf, Mark" <mark.langsdorf@....com>
To:	"Lee Revell" <rlrevell@...-job.com>
cc:	linux-kernel@...r.kernel.org
Subject: RE: AMD X2 unsynced TSC fix?

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