Date: Fri, 25 Jan 2002 16:03:06 -0700 From: Chuck Paterson <cp@twistedbit.com> To: nate@yogotech.com (Nate Williams) Cc: Daniel Eischen <eischen@pcnet1.pcnet.com>, Terry Lambert <tlambert2@mindspring.com>, Dan Eischen <eischen@vigrid.com>, k Macy <kip_macy@yahoo.com>, Peter Wemm <peter@wemm.org>, Julian Elischer <julian@vicor-nb.com>, arch@FreeBSD.ORG Subject: Re: KSE question Message-ID: <200201252303.g0PN36P13616@grendel.twistedbit.com> In-Reply-To: Your message of "Fri, 25 Jan 2002 15:36:48 MST." <15441.56832.170618.611705@caddis.yogotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
You could allow a user process post and address to the kernel for the kernel to update when the FPU goes into the used state. Or for that matter arrange for 1 or more page of kernel space to hold this type of stuff that an a libray to look at them This way you can get at the used bit without the cost of a system call. Chuck ----- Begin Included Message ----- There's lots of talk about using this 'FPU used' flag, but at least my read of things from the long discussion before was that it may not be possible to implement this on the x86 architectures we currently support. It sounds like a great idea, *IF* if can be done. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message ----- End Included Message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201252303.g0PN36P13616>