From owner-freebsd-smp Wed May 28 11:13:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA24833 for smp-outgoing; Wed, 28 May 1997 11:13:45 -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 LAA24827 for ; Wed, 28 May 1997 11:13:43 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.5/8.8.5) with ESMTP id MAA13794; Wed, 28 May 1997 12:13:38 -0600 (MDT) Message-Id: <199705281813.MAA13794@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: mef@cs.washington.edu cc: smp@FreeBSD.ORG, ulbright@cs.washington.edu Subject: Re: SMP_PRIVPAGES In-reply-to: Your message of "Wed, 28 May 1997 09:11:52 PDT." <199705281611.JAA29127@tweetie-bird.cs.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 May 1997 12:13:38 -0600 Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > What is the plan with using the SMP_PRIVPAGES stuff? Does it work? > (well, I'll find out in an hour or so). not yet, but hopefully soon. --- > As some of you know, we are using some of the FreeBSD SMP code to make > our own operating system (SPIN) work on multiprocessors. One thing interesting this is the first I've heard of this... --- > that I'm working on now is obtaining the CPUID in various components > (scheduler mostly right now). Rather than executing a bunch of > instructions to extract the logical CPUID from the apic_base, I'd > rather just place dereference CPU private data that contains the CPUs > logical id. My plan is to just use the existing SMP_PRIVPAGES support > to place CPU private data in those pages. thats exactly why we're creating them. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD