From owner-cvs-all Thu Mar 20 11:43:50 2003 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7480637B401; Thu, 20 Mar 2003 11:43:48 -0800 (PST) Received: from k6.locore.ca (k6.locore.ca [198.96.117.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30A4C43F3F; Thu, 20 Mar 2003 11:43:47 -0800 (PST) (envelope-from jake@k6.locore.ca) Received: from k6.locore.ca (localhost.locore.ca [127.0.0.1]) by k6.locore.ca (8.12.8/8.12.8) with ESMTP id h2KJmcxS062867; Thu, 20 Mar 2003 14:48:38 -0500 (EST) (envelope-from jake@k6.locore.ca) Received: (from jake@localhost) by k6.locore.ca (8.12.8/8.12.8/Submit) id h2KJmcYM062866; Thu, 20 Mar 2003 14:48:38 -0500 (EST) Date: Thu, 20 Mar 2003 14:48:38 -0500 From: Jake Burkholder To: Andrew Gallatin Cc: Peter Grehan , src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/powerpc/powerpc fpu.c genassym.c swtch.S trap.c Message-ID: <20030320144838.O76446@locore.ca> References: <200303201028.h2KASKU9090258@repoman.freebsd.org> <20030320110240.A3985@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030320110240.A3985@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Mar 20, 2003 at 11:02:40AM -0500 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Apparently, On Thu, Mar 20, 2003 at 11:02:40AM -0500, Andrew Gallatin said words to the effect of; > Peter Grehan [grehan@FreeBSD.org] wrote: > > grehan 2003/03/20 02:28:20 PST > > > > FreeBSD src repository > > > > Modified files: > > sys/powerpc/powerpc fpu.c genassym.c swtch.S trap.c > > Log: > > Enable the FPU on first use per-thread and save state across context > > switches. Not as lazy as it could be. Changing FPU state with sigcontext > > still TODO. > > I think I agree w/you that lazy might not be the way to go. I'm still > planning to see what the affect of non-lazy (proactive?) FPU state > switching would be on the alpha port. By non-lazy do you mean restore the state immediately in cpu_switch? Instead of allowing the process to return to userland with floating point disabled and restoring on the first FP instruction? Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message