From owner-freebsd-smp Sun Sep 29 02:22:31 1996 Return-Path: owner-smp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA09829 for smp-outgoing; Sun, 29 Sep 1996 02:22:31 -0700 (PDT) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA09746; Sun, 29 Sep 1996 02:22:22 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id DAA17778; Sun, 29 Sep 1996 03:22:15 -0600 Message-Id: <199609290922.DAA17778@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: Peter Wemm cc: freebsd-smp@freefall.freebsd.org Subject: Re: cvs commit: sys/kern init_main.c kern_shutdown.c In-reply-to: Your message of "Sun, 29 Sep 1996 01:36:28 PDT." <199609290836.BAA13518@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Sep 1996 03:22:14 -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, Peter said: > Modified: kern init_main.c kern_shutdown.c > Log: > Attempt to fix the boot() problems in obtaining cpu#0, as pointed out > by: Hidetoshi Shimokawa > > I'm not 100% sure I've got this right, cpunumber() now returns a logical > cpu id, doesn't it? Steve?? Therefore, the boot cpu logical id is always > zero, right?? :-) yes, this is correct. The BSP (Boot Strap Processor) is always logical #0. APs (Application Processors) follow in logical order 1,2,3,n. These are the numbers returned by 'cpunumber()' and 'GETPROCID()'. If you need the actual APIC ID of a logical CPU, use 'CPU_TO_ID( logical# )'. Inversly, to get the logical # from an APIC ID use 'ID_TO_CPU( physical# )'. These values are now parsed from the MP table during boot, supporting machines with SPARSE and/or un-ordered CPU/IO APIC ID numbering (most P6 machines). It also supports non-standard APIC addresses. Note that we are a long way from supporting more than 2 CPUs, ie. if you try to set NCPU=4 it will probably go down in flames. I'll check the patch in a moment and confirm. -- Steve Passe | powered by smp@csn.net | FreeBSD