Date: Fri, 05 May 2006 15:03:41 +0200 From: Attila Nagy <bra@fsn.hu> To: Scott Long <scottl@samsco.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Core Duo - only one cpu being used Message-ID: <445B4D2D.8070502@fsn.hu> In-Reply-To: <445AD83A.7090607@samsco.org> References: <445AB56F.8090907@centtech.com> <445AC174.5050102@pacific.net.sg> <445AC46F.30702@centtech.com> <445AD048.80305@pacific.net.sg> <445AD1AC.1070902@centtech.com> <445AD300.1020808@pacific.net.sg> <445AD50B.2060107@centtech.com> <445AD6B4.7050407@pacific.net.sg> <445AD83A.7090607@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, On 05/05/06 06:44, Scott Long wrote: > CPU1 is being treated as a hyperthreading core instead of a real core, > and is being disabled per our policy on Intel hyperthreading. By > 'disabled' I mean that it is started, but it is being excluded from > scheduling decisions, and thus is only running its idle proc. It's > also handling any interrupts that come to it, such as timer and IPI > interrupts, so it's at 99% instead of 100% for the idle proc. There > is nothing broken about the number you are seeing, your system is > just running under a scheduling policy that it should not be. > > This should have been fixed a week or so ago by a commit to HEAD, > RELENG_6, and RELENG_6_1 by Colin Percival. How old is kernel? Isn't this fixed by jkim's commit? I don't have any Core Duos here, but on a Xeon LV (Sossaman) with CURRENT, everything is OK: http://www.freebsd.org/cgi/query-pr.cgi?pr=96203 BTW, just set machdep.hyperthreading_allowed=1 until the fix arrives. -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?445B4D2D.8070502>