Messages in this thread | | | Date | Thu, 28 May 2015 07:45:18 -0700 | From | Dave Hansen <> | Subject | Re: [PATCH 02/19] x86, fpu: Wrap get_xsave_addr() to make it safer |
| |
On 05/28/2015 01:41 AM, Ingo Molnar wrote: > What you want here is to make the (in-memory) FPU state valid and current, before > reading it, and the function to use for that is fpu__activate_fpstate_read() > (available in the latest tip:x86/fpu tree).
Do we really want to unconditionally activate the FPU?
Let's say supporting MPX didn't require eager mode and someone called get_xsave_addr(). We would ideally want to keep the FPU inactive and just return NULL. Right?
| |