From owner-freebsd-amd64@FreeBSD.ORG  Mon Mar 13 15:16:16 2006
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
X-Original-To: freebsd-amd64@freebsd.org
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5F1BC16A41F
	for <freebsd-amd64@freebsd.org>; Mon, 13 Mar 2006 15:16:16 +0000 (UTC)
	(envelope-from petefrench@ticketswitch.com)
Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F080543D45
	for <freebsd-amd64@freebsd.org>; Mon, 13 Mar 2006 15:16:15 +0000 (GMT)
	(envelope-from petefrench@ticketswitch.com)
Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk)
	by mail.ticketswitch.com with esmtp (Exim 4.52 (FreeBSD))
	id 1FIomN-000Mh2-AI; Mon, 13 Mar 2006 15:16:15 +0000
Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim
	4.52 (FreeBSD)) id 1FIomN-00015b-4x; Mon, 13 Mar 2006 15:16:15 +0000
To: wmoran@collaborativefusion.com
In-Reply-To: <20060313094356.d7f0988a.wmoran@collaborativefusion.com>
Message-Id: <E1FIomN-00015b-4x@dilbert.firstcallgroup.co.uk>
From: Pete French <petefrench@ticketswitch.com>
Date: Mon, 13 Mar 2006 15:16:15 +0000
Cc: bseklecki@collaborativefusion.com, freebsd-amd64@freebsd.org
Subject: Re: How is hyperthreading handled on amd64?
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Mar 2006 15:16:17 -0000

> I don't see this behaviour on i386 - my desktop, for example uses only
> CPU 0 if the sysctl is 0, and switches between 0 and 1 when the sysctl
> is 1.

Uh, a typo on my part - substitute *machine* for *kernel*. Sorry!

A machine with one physical processor works fine - ccan enable and disable
hyperthreading as pper the manual. A machine with two physical processors
always gets hyperthreading enabled though. All of these machines are
running 6.0 currently - though I will verify that the bug is still there
on 6.1 when I get a moment to do an update on them.

-pete.