From: Dave Hansen <dave.hansen@intel.com>
To: Ingo Molnar <mingo@kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Yu, Yu-cheng" <yu-cheng.yu@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>
Subject: x86 fpu: command-line parameters broken post-FPU-rewrite
Date: Tue, 8 Dec 2015 12:43:13 -0800 [thread overview]
Message-ID: <566740E1.40608@intel.com> (raw)
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?
next reply other threads:[~2015-12-08 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 20:43 Dave Hansen [this message]
2015-12-09 8:32 ` x86 fpu: command-line parameters broken post-FPU-rewrite Ingo Molnar
2015-12-09 19:14 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=566740E1.40608@intel.com \
--to=dave.hansen@intel.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox