From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752774AbbLHUnP (ORCPT ); Tue, 8 Dec 2015 15:43:15 -0500 Received: from mga01.intel.com ([192.55.52.88]:20603 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752594AbbLHUnN (ORCPT ); Tue, 8 Dec 2015 15:43:13 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,400,1444719600"; d="scan'208";a="837066998" From: Dave Hansen Subject: x86 fpu: command-line parameters broken post-FPU-rewrite To: Ingo Molnar , the arch/x86 maintainers , LKML , "Yu, Yu-cheng" , "Yu, Fenghua" Message-ID: <566740E1.40608@intel.com> Date: Tue, 8 Dec 2015 12:43:13 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hey Ingo, We were starting to look at reenabling XSAVES support and tried to use the 'noxsave' and 'noxsaves' kernel command-line options. The rewrite moved the FPU initialization to before we even are parsing command-line options, even the early_param()s. Do you have any preferences on how it gets fixed? The most obvious thing would be to just defer as much of the FPU setup as we can until after parse_early_param() has happened. The only other think I can think of doing would be to try to do some *really* early, simple, command-line parsing to look for 'noxsave' and friends. Thoughts?