Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Mar 2003 14:48:38 -0500
From:      Jake Burkholder <jake@locore.ca>
To:        Andrew Gallatin <gallatin@cs.duke.edu>
Cc:        Peter Grehan <grehan@FreeBSD.org>, 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>
In-Reply-To: <20030320110240.A3985@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Mar 20, 2003 at 11:02:40AM -0500
References:  <200303201028.h2KASKU9090258@repoman.freebsd.org> <20030320110240.A3985@grasshopper.cs.duke.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030320144838.O76446>