On 10/04/2018 07:05 AM, Sebastian Andrzej Siewior wrote: > The fpu->initialized flag should not be changed underneath us. This might be a > fallout during the removal of the LazyFPU support. The FPU is marked > initialized as soon as the state has been set to an initial value. It does not > signal if the CPU's FPU registers are loaded. If this is true, then the check for fpu->initialized should also go away. If we were paranoid, we might also add a WARN_ON_ONCE() to make sure our assumption holds true.
