From owner-freebsd-arch Mon Jan 7 12:18:47 2002 Delivered-To: freebsd-arch@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id C516F37B405 for ; Mon, 7 Jan 2002 12:18:38 -0800 (PST) Received: from caddis.yogotech.com (caddis.yogotech.com [206.127.123.130]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id NAA14766; Mon, 7 Jan 2002 13:18:33 -0700 (MST) (envelope-from nate@yogotech.com) Received: (from nate@localhost) by caddis.yogotech.com (8.11.6/8.11.6) id g07KIWh99041; Mon, 7 Jan 2002 13:18:32 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15418.663.130281.835301@caddis.yogotech.com> Date: Mon, 7 Jan 2002 13:18:31 -0700 To: Alfred Perlstein Cc: Nate Williams , Dan Eischen , Peter Wemm , Archie Cobbs , arch@FreeBSD.ORG Subject: Re: Request for review: getcontext, setcontext, etc In-Reply-To: <20020107130208.E18706@elvis.mu.org> References: <20020106232937.9F87D38CC@overcee.netplex.com.au> <3C390746.5FE7648C@vigrid.com> <15417.59947.662052.836634@caddis.yogotech.com> <20020107130208.E18706@elvis.mu.org> X-Mailer: VM 6.96 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > > Also, I noticed that the i386 patch doesn't save FP state (!) which is > > > > one of the primary reasons for get/setcontext(). I'm not sure if this > > > > can be efficiently done since this user-level function will not know if > > > > the current context has touched the FPU yet.. > > > > > > Neither does the kernel, does it? I thought I saw comments in the > > > kernel (was it alpha?) about it being too bad that we couldn't tell > > > if the FPU was used. In libc_r, we currently only save and restore the > > > FP state when the context is generated from a signal handler (or perhaps > > > in the case of KSEs, when the thread was preempted). > > > > Hmm, IIRC, Java's green threads saves the FP context everytime it does a > > thread switch, since it has no way of knowing if the thread was doing FP > > context. Is there a way to force get/setcontext to always/conditionally > > save the FP context, for applications that either know they need to have > > it saved? > > Well, one trick might be to do this: > > 1) Request that the OS turn off the FP enabled bit when running new > threads. In userland threads, there is no way to turn it off on a thread basis, so it's either on/off for the entire process. > 2) If you get an FP not present exception you mark that thread as > using FP. At this point, we'd have to turn it on for all threads, since any future thread that uses the context would also need to save/restore the thread. (Since, FPU would be turned on for this 'process'.) > 3) In the threads scheduler and at context switch time between it (the > thread) and any other thread not using FP you request the behavior > of point #1. > > So you would only have a syscall when switching between FP and non-FP > threads. > > Is this possible? In the future it may be possible, if we keep track of FP-usage on a thread basis instead of a process basis. This requires kernel threads. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message