Re: [PATCH 1/4] x86, fpu: introduce per-cpu "bool in_kernel_fpu"

2014-09-02 Thread Suresh Siddha
On Fri, Aug 29, 2014 at 11:16 AM, Oleg Nesterov wrote: > interrupted_kernel_fpu_idle() tries to detect if kernel_fpu_begin() > is safe or not. In particulat it should obviously deny the nested > kernel_fpu_begin() and this logic doesn't look clean. > > If use_eager_fpu() == T we rely on a)

Re: [PATCH 1/4] x86, fpu: introduce per-cpu bool in_kernel_fpu

2014-09-02 Thread Suresh Siddha
On Fri, Aug 29, 2014 at 11:16 AM, Oleg Nesterov o...@redhat.com wrote: interrupted_kernel_fpu_idle() tries to detect if kernel_fpu_begin() is safe or not. In particulat it should obviously deny the nested kernel_fpu_begin() and this logic doesn't look clean. If use_eager_fpu() == T we rely on

[PATCH 1/4] x86, fpu: introduce per-cpu "bool in_kernel_fpu"

2014-08-29 Thread Oleg Nesterov
interrupted_kernel_fpu_idle() tries to detect if kernel_fpu_begin() is safe or not. In particulat it should obviously deny the nested kernel_fpu_begin() and this logic doesn't look clean. If use_eager_fpu() == T we rely on a) __thread_has_fpu() check in interrupted_kernel_fpu_idle(), and b) on

[PATCH 1/4] x86, fpu: introduce per-cpu bool in_kernel_fpu

2014-08-29 Thread Oleg Nesterov
interrupted_kernel_fpu_idle() tries to detect if kernel_fpu_begin() is safe or not. In particulat it should obviously deny the nested kernel_fpu_begin() and this logic doesn't look clean. If use_eager_fpu() == T we rely on a) __thread_has_fpu() check in interrupted_kernel_fpu_idle(), and b) on