From owner-freebsd-smp Tue Jun 29 18:40:43 1999 Delivered-To: freebsd-smp@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 6F426150AA for ; Tue, 29 Jun 1999 18:40:39 -0700 (PDT) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 10z9N3-000A2a-00; Tue, 29 Jun 1999 21:41:05 -0400 To: Alfred Perlstein Cc: freebsd-smp@FreeBSD.ORG From: "Gary Palmer" Subject: Re: high-efficiency SMP locks - submission for review In-reply-to: Your message of "Tue, 29 Jun 1999 03:20:16 CDT." Date: Tue, 29 Jun 1999 21:41:01 -0400 Message-ID: <38599.930706861@noop.colo.erols.net> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ CC Trimmed ] Alfred Perlstein wrote in message ID : > We have a nifty loader now, why not have it determine the CPU > type and boot the appropriate kernel? It could easily been done > in forth if the loader exported the CPU type in an enviorment > flag... > > Doesn't Sun do this? Nope. Suns base `kernel' image (/kernel/genunix, from memory) has all the threading and locking primitives in it, as well as some syscall handlers (I forget which). Everything dynamically loaded after that is the same across most platforms, with only machine-dependant drivers really changing between systems. The boot loader differs between hardware platforms, but thats mostly an instruction set issue I believe. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message