From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 19 19:11:36 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5980716A406; Thu, 19 Apr 2007 19:11:36 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 18B4413C45D; Thu, 19 Apr 2007 19:11:36 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 8270E2083; Thu, 19 Apr 2007 21:11:32 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 706602049; Thu, 19 Apr 2007 21:11:32 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id 59FC75410; Thu, 19 Apr 2007 21:11:32 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Mark Tinguely References: <200704191736.l3JHad0E057895@casselton.net> Date: Thu, 19 Apr 2007 21:11:32 +0200 In-Reply-To: <200704191736.l3JHad0E057895@casselton.net> (Mark Tinguely's message of "Thu, 19 Apr 2007 12:36:39 -0500 (CDT)") Message-ID: <86y7ko2n8b.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org, MTaylor@bytecraft.com.au Subject: Re: IBM / FreeBSD Install problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2007 19:11:36 -0000 Mark Tinguely writes: > I suggested that in email too, but looking closer, I think the MAXCPU > needs to be increased because the cpu number uses the apic_id. Or could > that be changed with a logical CPU to APIC ID lookup? > > Isn't the APIC IDs programmable? not that I am suggesting that, I > can think of headaches of all the places (like interrupt tables) > where it needs to be changed, not to mention the worry that the > lower APIC IDs were assigned to IOAPICs. I don't know, you'd have to ask jhb@ about the details. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no