From owner-freebsd-smp@FreeBSD.ORG Thu Oct 12 16:54:03 2006 Return-Path: X-Original-To: freebsd-smp@freebsd.org Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30C2016A417; Thu, 12 Oct 2006 16:54:03 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6875343D7C; Thu, 12 Oct 2006 16:54:01 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb.matik.com.br (anb.matik.com.br [200.152.88.34] (may be forged)) by msrv.matik.com.br (8.13.8/8.13.1) with ESMTP id k9CGrscJ003348; Thu, 12 Oct 2006 13:53:55 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-smp@freebsd.org Date: Thu, 12 Oct 2006 13:53:38 -0300 User-Agent: KMail/1.9.4 References: <20061009114520.1355.qmail@web8608.mail.in.yahoo.com> <200610102015.36589.joao@matik.com.br> <200610120924.48482.jhb@freebsd.org> In-Reply-To: <200610120924.48482.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200610121353.40008.joao@matik.com.br> X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,AWL autolearn=unavailable version=3.1.3 X-Spam-Checker-Version: Antispam Datacenter Matik msrv.matik.com.br X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Cc: Subject: Re: Hyperthreading Issues (on Athlon64?) X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Oct 2006 16:54:03 -0000 On Thursday 12 October 2006 10:24, John Baldwin wrote: > > > > > > Err, no. =A0The HTT there stands for HyperThreading Technology. > > > > you say it right: "stands for" in this case > > > > But I think it "is" the other way round, in terms of abreviation: > > > > HTT =3D Hyper Transport Technology > > HT =3D Hyper Threading (Technology) > > I don't think this really bothers anyone. > sure, until bitten by the confusion > > You didn't read anything I said earlier. When dual-core came out, to make > it easier for OS's to detect it (probably Windows), AMD made a dual-core > CPU look just like an Intel CPU with 2 hyperthreads including using the > CPUID HT flag in cpuid that _Intel_ had reserved. Even ports/misc/cpuid > calls the flag HT. Sheesh. nonoooooo, it reads the HTT flag=20 so confusion is perfect now ... please see the funny side of it=20 the processor's cpuid function, when returning the HTT bit, reports dual-co= re=20 single thread (AMD) or single-core dual-thread (Intel), and not that AMD=20 makes it appear like an Intel-HT CPU ... but then ports/cpuid still reports: =20 HT Hyper Threading (on Intel CPUs) isn't it funny? =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br