From 5c564e29454aad4a7cbd310c7c03407b3ce7f4c2 Mon Sep 17 00:00:00 2001 From: jmg Date: Thu, 23 Oct 2014 17:24:50 +0000 Subject: [PATCH] minor updates to make it more explicit that when using fpu_kern_thread, you don't need to use fpu_kern_enter/_leave... Reviewed by: kib --- share/man/man9/fpu_kern.9 | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/share/man/man9/fpu_kern.9 b/share/man/man9/fpu_kern.9 index 207e5e805422..748e6fca4b43 100644 --- a/share/man/man9/fpu_kern.9 +++ b/share/man/man9/fpu_kern.9 @@ -23,7 +23,7 @@ .\" .\" $FreeBSD$ .\" -.Dd June 23, 2014 +.Dd October 23, 2014 .Dt FPU_KERN 9 .Os .Sh NAME @@ -157,12 +157,17 @@ There are no errors defined for the function, it always returns 0. .Pp The .Fn fpu_kern_thread -function provides an optimization for threads which never leave to +function enables an optimization for threads which never leave to the usermode. -Such thread can reuse the usermode save area for the FPU state, -which is allowed by the function call. -There is no flags defined for the function, and no error states +The current thread will reuse the usermode save area for the kernel FPU state +instead of requiring an explicitly allocated context. +There are no flags defined for the function, and no error states that the function returns. +Once this function has been called, neither +.Fn fpu_kern_enter +nor +.Fn fpu_kern_leave +is required to be called and the fpu is available for use in the calling thread. .Pp The .Fn is_fpu_kern_thread