From owner-freebsd-smp Wed Apr 3 12:14:19 2002 Delivered-To: freebsd-smp@freebsd.org Received: from swan.prod.itd.earthlink.net (swan.mail.pas.earthlink.net [207.217.120.123]) by hub.freebsd.org (Postfix) with ESMTP id 4E44E37B41A; Wed, 3 Apr 2002 12:14:15 -0800 (PST) Received: from pool0355.cvx40-bradley.dialup.earthlink.net ([216.244.43.100] helo=mindspring.com) by swan.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16sr94-0000U2-00; Wed, 03 Apr 2002 12:14:14 -0800 Message-ID: <3CAB627F.79EF279@mindspring.com> Date: Wed, 03 Apr 2002 12:13:51 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin , "Andrew R. Reiter" , smp@FreeBSD.ORG, Jake Burkholder Subject: Re: Where to initialize certain locks... References: <3CAB621A.6F84F736@mindspring.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Terry Lambert wrote: > John Baldwin wrote: > > We need mutexes prior to mi_startup(). > > There are really two problems with this theory: > > 1) You can't use them before the mutex system is initialized, > which happens from mi_startup. > > 2) There are no contended resources until after mi_startup > starts the other CPU(s). Forgot: 3) I never said to call the init routine at mi_startup(); you could actually call it as early as you wanted, as long as there were no dependencies on things like memory allocation. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message