Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752749AbcCLPIW (ORCPT ); Sat, 12 Mar 2016 10:08:22 -0500 Received: from mail-wm0-f67.google.com ([74.125.82.67]:36849 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752587AbcCLPIO (ORCPT ); Sat, 12 Mar 2016 10:08:14 -0500 Date: Sat, 12 Mar 2016 16:08:09 +0100 From: Ingo Molnar To: Linus Torvalds Cc: Borislav Petkov , "Bryan O'Donoghue" , Andy Lutomirski , Andy Shevchenko , "linux-kernel@vger.kernel.org" , "x86@kernel.org" , Fenghua Yu , "H. Peter Anvin" , Thomas Gleixner , Andrew Morton , Dave Hansen , Oleg Nesterov , "Yu, Yu-cheng" Subject: Re: [PATCH] x86/FPU: Fix FPU handling on legacy FPU machines Message-ID: <20160312150809.GA7015@gmail.com> References: <20160310125610.GA26708@pd.tnic> <20160310145940.GB26708@pd.tnic> <20160311090840.GA8486@gmail.com> <20160311094802.GA4312@pd.tnic> <1457694124.2007.12.camel@nexus-software.ie> <20160311112610.GC4312@pd.tnic> <20160311113206.GD4312@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1114 Lines: 31 * Linus Torvalds wrote: > On Fri, Mar 11, 2016 at 3:32 AM, Borislav Petkov wrote: > > 486 cores like Intel Quark support only the very old, legacy x87 FPU > > (FSAVE/FRSTOR, CPUID bit FXSR is not set). And our FPU code wasn't > > handling the saving and restoring there properly. First, Andy Shevchenko > > reported a splat: > > > > WARNING: CPU: 0 PID: 823 at arch/x86/include/asm/fpu/internal.h:163 fpu__clear+0x8c/0x160 > > > > which was us trying to execute FXRSTOR on those machines even though > > they don't support it. > > > > After taking care of that, Bryan O'Donoghue reported that a simple FPU > > test still failed because we weren't initializing the FPU state properly > > on those machines. > > Obvious Ack to the patch, along with a "how did this ever work > before?" comment.. So the window for 'real' breakage was relatively short: this is an older bug but only became a serious bug with the following upcoming commit: 58122bf1d856 x86/fpu: Default eagerfpu=on on all CPUs ... but it's nice to have it fixed nevertheless! Thanks, Ingo