Date: Tue, 12 Sep 2000 16:31:01 +0200 From: Poul-Henning Kamp <phk@freebsd.org> To: smp@freebsd.org, arch@freebsd.org Subject: system initialization order. Message-ID: <78946.968769061@critter>
next in thread | raw e-mail | index | archive | help
With SMPng I think we need to take a good hard stare at the order in which we initialize the system, a lot of the reasons behind the current order are invalid, and some new reasons for a new order are not honoured. Roughly speaking, I think we need something like this order: init console print copyright initialize VM/malloc(9) init other stuff needed for: setup proc0 setup proc1 (park it on a semaphore for now) setup idle procs enable scheduler init hardclock enable hardclock interrupt initialize timecounters This should now represent a sufficiently "normal" environment that the order of the rest doesn't really matter very much: init network protocols init pseudodrivers probe/attach real drivers ata/scsi delayed probing needs thought about here. locate & mount root let proc1 loose Comments ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?78946.968769061>