From owner-cvs-sys Tue Aug 12 09:16:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA01524 for cvs-sys-outgoing; Tue, 12 Aug 1997 09:16:58 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01518; Tue, 12 Aug 1997 09:16:49 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.6/8.8.5) with ESMTP id KAA19532; Tue, 12 Aug 1997 10:16:43 -0600 (MDT) Message-Id: <199708121616.KAA19532@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Michael Smith cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-sys@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern init_main.c In-reply-to: Your message of "Wed, 13 Aug 1997 01:27:04 +0930." <199708121557.BAA08791@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 12 Aug 1997 10:16:43 -0600 Sender: owner-cvs-sys@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > > no, its a hack to prevent code in configure() from panic()ing when trying > > to dereference (struct proc*)p->xxx thingies. there is code that does this > > early in the boot process that knows that curproc is incomplete and is careful > > to not use the missing parts. There is nothing SMP specific about this. The > > only reason its needed is that the UP kernel "sets" it at compile time via: > > Ok, perhaps I should be more explicit : > > - at what point is curproc filled out adequately for use with lockmgr() > and friends? > - if I don't know "when" I am, how can I work this out? there is a variable named 'cold' that other code seems to use to determine when it can do various things. I honestly haven't looked at this in detail yet, I'm still struggling with lower level issues. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD