From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Ingo Molnar <mingo@kernel.org>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [all better] Re: regression: massive trouble with fpu rework
Date: Sun, 28 Jun 2015 05:11:57 +0200 [thread overview]
Message-ID: <1435461117.3418.32.camel@gmail.com> (raw)
In-Reply-To: <20150627210238.GB3054@khazad-dum.debian.net>
On Sat, 2015-06-27 at 18:02 -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 27 Jun 2015, Mike Galbraith wrote:
> > > > BIOS setting "Limit CPUID Maximum" upsets new fpu code mightily.
> >
> > That BIOS setting is annotated with the helpful text "Disabled for
> > Windows XP". It makes box say interesting things during boot, like...
> >
> > x86/fpu: XSTATE_CPUID missing!
> >
> >
> > ..or with HEAD, it triggers warning..
> >
> > if (boot_cpu_data.cpuid_level < XSTATE_CPUID) {
> > WARN_ON_FPU(1);
> > return;
> > }
> >
> > ..and all kinds of bad juju follows. I have no idea what the thing does
> > beyond what I can interpolate from the word 'limit'.
>
> Well, it is supposed to disable CPUID levels >= 0x04. This thing should
> *NEVER* be enabled, the last operating system that required it to be enabled
> was Windows 98.
>
> Can/do we override that crap during cpu init? If we cannot/don't, maybe
> instead of limping along with CPUID crippled, it would be better to either
> output a very nasty warning, or outright stop booting [with an appropriate
> error message] ?
Why get all upset? We didn't even notice before, nor did/does that
other OS. A casual "BTW, your BIOS sucks.." should suffice, no?
-Mike
next prev parent reply other threads:[~2015-06-28 3:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 6:25 regression: massive trouble with fpu rework Mike Galbraith
2015-06-27 8:18 ` [all better] " Mike Galbraith
2015-06-27 8:25 ` Ingo Molnar
2015-06-27 8:55 ` Mike Galbraith
2015-06-27 9:37 ` Borislav Petkov
2015-06-27 11:01 ` Mike Galbraith
2015-06-27 21:02 ` Henrique de Moraes Holschuh
2015-06-28 3:11 ` Mike Galbraith [this message]
2015-06-28 15:06 ` Henrique de Moraes Holschuh
2015-06-28 15:39 ` Mike Galbraith
2015-06-29 1:12 ` Henrique de Moraes Holschuh
2015-06-29 6:40 ` Ingo Molnar
2015-06-29 8:25 ` Mike Galbraith
2015-06-29 8:33 ` Borislav Petkov
2015-06-29 8:41 ` Mike Galbraith
2015-06-29 9:35 ` Ingo Molnar
2015-06-29 9:57 ` Borislav Petkov
2015-06-29 19:48 ` H. Peter Anvin
2015-06-30 5:14 ` Ingo Molnar
2015-06-29 12:27 ` Mike Galbraith
2015-06-29 13:09 ` Borislav Petkov
2015-06-30 5:16 ` Ingo Molnar
2015-06-30 20:22 ` H. Peter Anvin
2015-07-09 13:13 ` Henrique de Moraes Holschuh
2015-06-29 19:50 ` H. Peter Anvin
2015-06-30 5:18 ` Ingo Molnar
2015-06-30 5:24 ` [tip:x86/urgent] x86/fpu: Fix FPU related boot regression when CPUID masking BIOS feature is enabled tip-bot for Ingo Molnar
2015-06-27 8:18 ` regression: massive trouble with fpu rework Ingo Molnar
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=1435461117.3418.32.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
/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