On Thu, May 09 2024 at 10:36, Dave Hansen wrote: > Three lines of code: > > 1. IFS declares its need to own the FPU for a moment, like any > other kernel_fpu_begin() user. It's not a special snowflake. > It is boring. > 2. IFS zaps the FPU state > 3. IFS gives up the FPU > > Am I out of my mind? What am I missing? Why bother with _anything_ > more complicated than this? Right. Keep it simple :)
