From owner-freebsd-questions@FreeBSD.ORG Tue May 24 17:44:27 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C7EE16A41C for ; Tue, 24 May 2005 17:44:27 +0000 (GMT) (envelope-from kellers@njit.edu) Received: from mail-gw5.njit.edu (mail-gw5.njit.edu [128.235.251.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id B18D043D1D for ; Tue, 24 May 2005 17:44:22 +0000 (GMT) (envelope-from kellers@njit.edu) Received: from admcluster.njit.edu (admactive.njit.edu [128.235.184.198]) by mail-gw5.njit.edu (8.12.10/8.12.4) with ESMTP id j4OHiHbE024763; Tue, 24 May 2005 13:44:19 -0400 (EDT) Received: from dhcp114-129.njit.edu ([128.235.114.129]) by admcluster.njit.edu over TLS secured channel with Microsoft SMTPSVC(5.0.2195.5329); Tue, 24 May 2005 13:44:16 -0400 From: Tim Kellers Organization: CPE at NJIT To: freebsd-questions@freebsd.org Date: Tue, 24 May 2005 13:43:56 -0400 User-Agent: KMail/1.8 References: <200505241053.36377.kirk@strauser.com> <200505241159.24346.kellers@njit.edu> <200505241200.55346.kirk@strauser.com> In-Reply-To: <200505241200.55346.kirk@strauser.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200505241343.58666.kellers@njit.edu> X-OriginalArrivalTime: 24 May 2005 17:44:17.0096 (UTC) FILETIME=[35005480:01C56088] Cc: Subject: Re: Top only showing one active CPU on HTT system X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2005 17:44:27 -0000 On Tuesday 24 May 2005 01:00 pm, Kirk Strauser wrote: > On Tuesday 24 May 2005 10:59, Tim Kellers wrote: > > The acpi_load="YES" in /boot/loader.conf might do the trick. > > Actually, it turns out that I have to set machdep.hyperthreading_allowed=1 > for HTT to work now. > > Speaking of which, is that tunable documented anywhere besides the HTT > security PR? It's not in the 5.4-STABLE /usr/src/UPDATING or anyplace else > I've looked, so I was more than a bit surprised to find that such an > important default was changed without much notice. I imagine a lot of > people read the PR much as I did: "blah, blah, theoretical, doesn't affect > me, next message"... I even read the SA and it managed to completely pass through my head without hitting one brain cell.