From owner-cvs-all Wed Jul 29 23:29:19 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12278 for cvs-all-outgoing; Wed, 29 Jul 1998 23:29:19 -0700 (PDT) (envelope-from owner-cvs-all) Received: from antipodes.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12268; Wed, 29 Jul 1998 23:29:16 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id XAA00495; Wed, 29 Jul 1998 23:28:44 -0700 (PDT) Message-Id: <199807300628.XAA00495@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: asami@FreeBSD.ORG (Satoshi Asami) cc: imp@village.org, committers@FreeBSD.ORG Subject: Re: very quick reboot In-reply-to: Your message of "Wed, 29 Jul 1998 10:18:07 PDT." <199807291718.KAA02374@silvia.HIP.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 23:28:44 -0700 From: Mike Smith Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > * You'd also have to bzero the bss section of the kernel as well as > * recreate the boot information that was passed to the kernel from the > * boot blocks. > > Ok. Mike Smith also commented that we want to skip over that part. Either skip or recreate; certainly you can expect that the information that was there has been overwritten as the pages are reused. > * The only thing that I'd worry about would be hardware that is set to a > * known state by the bios that FreeBSD then sets to a different known > * state which would be FUBAR'd if FreeBSD were to set that state again. > > Hmm. I wouldn't be *too* worried about this. > * Video might also be a problem, but since we can now make 16-bit BIOS > * calls, it should be less of a problem. > > I'm not sure what you mean, but I'm assuming the X server is shut down > properly, so that should reset the video state, right? If the system is in mode known to the console when you restart, you should be fine (eg. text mode). > By the way, I don't suppose we can skip the probes (with calls to > suitable alternate initialization routines), right? That part of > memory is not write protected, so we can't assume it's not damaged if > the machine panic's. Actually, maybe we can, if it's a real clean > reboot. Hmm. Only ISA probe routines take any time, and only the 'wdc' ones take any real time. Many ISA probe routines perform initialisation as well as probing. PCI probe routines take no significant time at all; PCI attaches can take a long time depending on the hardware. Skipping attaches might be tricky. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com