From owner-freebsd-current Mon Sep 11 2:16:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (Postfix) with ESMTP id A412B37B422 for ; Mon, 11 Sep 2000 02:16:18 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 13YPhG-0001rw-0C; Mon, 11 Sep 2000 09:16:15 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA03103; Mon, 11 Sep 2000 10:16:55 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 11 Sep 2000 10:16:29 +0100 (BST) From: Doug Rabson To: John Baldwin Cc: Bruce Evans , Tor.Egge@fast.no, current@freebsd.org Subject: Re: Dirty buffers on reboot.. In-Reply-To: <200009110655.XAA36296@pike.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 10 Sep 2000, John Baldwin wrote: > > Hmmmm. At least on the x86, curproc is now set to proc0 before we probe > to see how much memory we have in init386(). In fact, we set curproc up > right after setting up the GDT, and before both the ldt and idt, so at least > on x86, we won't get a trap with curproc == NULL. :) On the alpha I'm not > as sure. Hmm, after looking, we set curproc in alpha_init(), but we do > it much later on. I'm not sure if we have enabled interrupts at that point > or not. Interrupts are certainly not enabled in alpha_init() - this is the earliest part of the alpha boot sequence. After alpha_init() returns, we switch to using proc0's stack for the first time (alpha_init() runs on the bootstrap stack) and call mi_startup() to get the rest of the kernel going. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8348 3944 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message