From: Andi Kleen <ak@suse.de>
To: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
Subject: Re: AMD X2 unsynced TSC fix?
Date: Fri, 27 Oct 2006 21:06:12 -0700
User-Agent: KMail/1.9.1
Cc: Lee Revell <rlrevell@joe-job.com>, Chris Friesen <cfriesen@nortel.com>,
       linux-kernel <linux-kernel@vger.kernel.org>,
       john stultz <johnstul@us.ibm.com>
References: <1161969308.27225.120.camel@mindpipe> <1161986902.27225.206.camel@mindpipe> <1162007907.26022.13.camel@localhost.localdomain>
In-Reply-To: <1162007907.26022.13.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200610272106.13115.ak@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 958
Lines: 25


> So far, has I can understand. Seems to me that my computer which have a
> Pentium D (Dual Core) on VIA chipset, also have unsynchronized TSC and
> with the patch of hrtimers on

Intel systems (except for some large highend systems) have synchronized TSCs. 
Only exception so far seems to be a few systems that are 
overclocked/overvolted and running outside their specification. 
When you do that you'e on your own and we're not interested in a bug
report.

There was also one BIOS found that had this problem, but it was old and rare
and got fixed with a upgrade.

> Just to point out. This could be more a problem of chipsets than CPUs
> (AMD or Intel). AMD just begin first using x86_64 archs :)

No.

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