From owner-freebsd-current Wed Apr 28 13:15:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id E7B351577D; Wed, 28 Apr 1999 13:15:01 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id PAA24466; Wed, 28 Apr 1999 15:14:54 -0500 (CDT) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.2/8.7.3) id PAA15451; Wed, 28 Apr 1999 15:14:54 -0500 (CDT) Date: Wed, 28 Apr 1999 15:14:54 -0500 From: Alan Cox To: Matthew Dillon Cc: Chuck Robey , Poul-Henning Kamp , Luoqi Chen , current@freebsd.org, smp@freebsd.org Subject: Re: HEADS UP! to commit SMP vmspace sharing patches Message-ID: <19990428151454.O1121@nonpc.cs.rice.edu> References: <199904281819.LAA07937@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199904281819.LAA07937@apollo.backplane.com>; from Matthew Dillon on Wed, Apr 28, 1999 at 11:19:17AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 28, 1999 at 11:19:17AM -0700, Matthew Dillon wrote: > I know this is a little late ... but I don't suppose there might be a > way to lock a TLB entry in place? That would solve the problem too. > Baring that, %fs is the way to go. > Unfortunately, on the x86, the answer is "No." The only serious alternative was to put the commonly used per processor variables and a pointer to the less commonly used ones at the base of each process's/thread's kernel stack, i.e., the upages, where you could mask off bits from the stack pointer to arrive at the correct address. You'd then have to "refresh" most of these variables on a context switch (in case the process migrated). Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message