From owner-freebsd-current@FreeBSD.ORG Fri Aug 22 19:23:50 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8D9816A4BF; Fri, 22 Aug 2003 19:23:50 -0700 (PDT) Received: from mx1.trigger.net (ns1.trigger.net [199.166.206.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4E3943FE3; Fri, 22 Aug 2003 19:23:49 -0700 (PDT) (envelope-from mikej@trigger.net) Received: from localhost (localhost [127.0.0.1]) by mx1.trigger.net (Postfix) with ESMTP id 6403A123865; Fri, 22 Aug 2003 22:23:39 -0400 (EDT) Received: from mx2.trigger.net (unixweb.trigger.net [199.166.206.9]) by mx1.trigger.net (Postfix) with ESMTP id 3484A12383E; Fri, 22 Aug 2003 22:23:37 -0400 (EDT) Received: by mx2.trigger.net (Postfix, from userid 80) id CF390625102; Fri, 22 Aug 2003 22:23:52 -0400 (EDT) Received: from 63.139.119.223 (SquirrelMail authenticated user mikej) by webmail.trigger.net with HTTP; Fri, 22 Aug 2003 22:23:52 -0400 (EDT) Message-ID: <1764.63.139.119.223.1061605432.squirrel@webmail.trigger.net> In-Reply-To: <20030822230857.GA99046@rot13.obsecurity.org> References: <1353.63.139.119.223.1061593383.squirrel@webmail.trigger.net> <20030822230857.GA99046@rot13.obsecurity.org> Date: Fri, 22 Aug 2003 22:23:52 -0400 (EDT) From: mikej@trigger.net To: "Kris Kennaway" User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Virus-Scanned: by AMaViS cc: mikej@trigger.net cc: current@freebsd.org Subject: Re: HTT on current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2003 02:23:51 -0000 > On Fri, Aug 22, 2003 at 07:03:03PM -0400, mikej@trigger.net wrote: >> > That is not an SMP kernel. An SMP kernel (with APIC_IO) would not >> print >> > out >> > the pcib0 interrupt routing messages. >> > >> > -- >> >> So whats the problem here? > > See above. >> How come the CPUs dont show up in top. > > See above. > >> How do i realy know the system sees 2, and actually utilizes them? >> Is there anything else i have to do other than enable SMP options in >> the kernel? > > Enable *ALL* of the SMP options in the kernel. See above. > > Kris Well i've enabled all SMP options, recompiled and rebooted. The CPUs now properly show up in dmesg and i can see the C header in top. However no processes seem to be being assigned to cpu 1. Why is the schedueler only using CPU 0? This wasnt the behaviour in stable. Thanks.