| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20150219200910.GA29373@redhat.com> Date: Thu, 19 Feb 2015 21:09:10 +0100 From: Oleg Nesterov <oleg@...hat.com> To: Ingo Molnar <mingo@...nel.org> Cc: Rik van Riel <riel@...hat.com>, dave.hansen@...ux.intel.com, sbsiddha@...il.com, luto@...capital.net, tglx@...utronix.de, mingo@...hat.com, hpa@...or.com, fenghua.yu@...el.com, x86@...nel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 6/6] x86,fpu: remove redundant increments of fpu_counter Borislav, Ingo, On 02/19, Ingo Molnar wrote: > > Is there consensus on the first 5 patches? Yes, but perhaps you can also look at another series [PATCH 1/3] x86, fpu: __kernel_fpu_begin() should clear fpu_owner_task even if use_eager_fpu() http://marc.info/?l=linux-kernel&m=142169357231860&w=2 [PATCH 2/3] x86, fpu: always allow FPU in interrupt if use_eager_fpu() http://marc.info/?l=linux-kernel&m=142169359331866&w=2 [PATCH 3/3] x86, fpu: don't abuse FPU in kernel threads if use_eager_fpu() http://marc.info/?l=linux-kernel&m=142169360931869&w=2 ? (off course I will be happy to resend) It was sent before the recently applied changes. And in fact in theory 728e53fef429a0f "x86/fpu: Also check fpu_lazy_restore() when use_eager_fpu()" depends on 1/3 above. Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists