From owner-freebsd-smp@FreeBSD.ORG  Fri Jun 13 12:38:40 2003
Return-Path: <owner-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 0D00B37B401; Fri, 13 Jun 2003 12:38:40 -0700 (PDT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 63AC743FB1; Fri, 13 Jun 2003 12:38:39 -0700 (PDT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 4C98C72FE7; Fri, 13 Jun 2003 12:38:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP
	id 4B44F72FE3; Fri, 13 Jun 2003 12:38:39 -0700 (PDT)
Date: Fri, 13 Jun 2003 12:38:39 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: Killing <killing@barrysworld.com>
In-Reply-To: <024201c330f4$e58fdcf0$7b07000a@int.mediasurface.com>
Message-ID: <20030613123718.S69249@carver.gumbysoft.com>
References: <F33F0D32429BD1458C34E3315053CE520FB830@xch-nw-28.nw.nos.boeing.com><012201c32fac$3f1cfa90$b3db87d4@vader>
	<024201c330f4$e58fdcf0$7b07000a@int.mediasurface.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
cc: freebsd-smp@freebsd.org
Subject: Re: SMP in 5.1 cant deactivate hyperthreading
X-BeenThere: freebsd-smp@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: FreeBSD SMP implementation group <freebsd-smp.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-smp>,
	<mailto:freebsd-smp-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-smp>
List-Post: <mailto:freebsd-smp@freebsd.org>
List-Help: <mailto:freebsd-smp-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-smp>,
	<mailto:freebsd-smp-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2003 19:38:40 -0000

On Thu, 12 Jun 2003, Killing wrote:

> > Halting them will still cause the CPUs to be detected. They just won't do
> > any useful work.
>
> Yep but the issue is that all the core admin tools are unaware of this and
> hence include the virtual cores in idle calcs etc making load monitoring
> impossible without nasty cludges :(
>
> So what's the way forward?
> 1. Dont just use halt have a compile or other directive to disable them?
> 2. Update all tools to be halt aware?
>
> Personally I'd go with 2 all be it more work / ramifications on other 3rd party
> tools as it gives the benefit of also working when physical CPU's are halted.

Guh.  Checking with some people here, it appears that the HT stuff is
still undergoing some tweaking. I'd suggest that you stay tuned for any
commits from john baldwin re: HT.

Your case appears to be unique.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org