From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753856AbcCISwY (ORCPT ); Wed, 9 Mar 2016 13:52:24 -0500 Received: from torg.zytor.com ([198.137.202.12]:47986 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750817AbcCISwT (ORCPT ); Wed, 9 Mar 2016 13:52:19 -0500 Subject: Re: [PATCH] x86/fpu: Revert earlier patch of Disable AVX when eagerfpu is off To: Ingo Molnar , Yu-cheng Yu References: <1453511438-25827-1-git-send-email-yu-cheng.yu@intel.com> <20160309124626.GA28660@gmail.com> Cc: linux-kernel@vger.kernel.org, x86@kernel.org, Thomas Gleixner , Dave Hansen , Ingo Molnar , Borislav Petkov , Sai Praneeth Prakhya , "Ravi V. Shankar" , Leonid Shatz , Fenghua Yu , Andy Lutomirski , Linus Torvalds , Andrew Morton , Peter Zijlstra From: "H. Peter Anvin" Message-ID: <56E070C1.6090302@zytor.com> Date: Wed, 9 Mar 2016 10:51:45 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <20160309124626.GA28660@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/09/2016 04:46 AM, Ingo Molnar wrote: > > * Yu-cheng Yu wrote: > >> AVX was mistakenly believed to be dependent on eagerfpu switch. >> This turns out to be false. The earlier patch should be reverted. >> >> Original patch: >> http://git.kernel.org/tip/394db20ca240741a08d472173db13d6f6a6e5a28 > > So the original patch had a whole host of explanations of why that change is > correct. This revert should explain where that argumentation was wrong. > > Also note that eagerfpu=off is on the way out, on v4.6 we'll switch all CPUs to > eagerfpu: > > 58122bf1d856 x86/fpu: Default eagerfpu=on on all CPUs > > and in the not so distant future, if everything goes fine with the eager mode, I'd > like to drop the lazy FPU context switching code altogether - which will simplify > a lot of code. At that point the 'eagerfpu' boot option will go away as well. > Last I heard the only use case which was seeing trouble with eagerfpu was KVM during service of I/O events. Might be worth checking into... -hpa