From owner-freebsd-arch Sun Jan 13 12:12:51 2002 Delivered-To: freebsd-arch@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id 8075A37B417 for ; Sun, 13 Jan 2002 12:12:47 -0800 (PST) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id HAA27621; Mon, 14 Jan 2002 07:12:30 +1100 (EDT) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37641) with ESMTP id <01KD1WTL4UJ4VFMSOV@cim.alcatel.com.au>; Mon, 14 Jan 2002 07:12:48 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.6/8.11.6) id g0DKCRR24555; Mon, 14 Jan 2002 07:12:27 +1100 Content-return: prohibited Date: Mon, 14 Jan 2002 07:12:26 +1100 From: Peter Jeremy Subject: Re: Request for review: getcontext, setcontext, etc In-reply-to: <20020111145159.N7984@elvis.mu.org>; from bright@mu.org on Fri, Jan 11, 2002 at 02:51:59PM -0800 To: Alfred Perlstein Cc: Nate Williams , Bakul Shah , Dan Eischen , arch@FreeBSD.ORG Mail-Followup-To: Alfred Perlstein , Nate Williams , Bakul Shah , Dan Eischen , arch@FreeBSD.ORG Message-id: <20020114071226.R561@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <3C37E559.B011DF29@vigrid.com> <200201112141.QAA25529@devonshire.cnchost.com> <15423.27120.926839.725176@caddis.yogotech.com> <20020111145159.N7984@elvis.mu.org> 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 On 2002-Jan-11 14:51:59 -0800, Alfred Perlstein wrote: >* Nate Williams [020111 14:46] wrote: >> >> The point is that this may not be a valid assumption w/regard to the FPU >> state. The necessity of saving/restoring the FPU state *IS* the primary >> subject of the the entire discussion, with the secondary part being that >> x86 hardware is broken, so it may not be possible to guarantee delivery >> of FPU exceptions to the same context that caused it. > >Couldn't this just be simply done by calling the "wait for fop to >complete" instruction before switching out an FP using thread? Given the current implementation (lazy FPU context load), if the thread hadn't previously use FP, then issuing an fwait will cause a "device not available" trap to the kernel. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message