Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1173316
| From | Mike Galbraith <umgwanakikbuti@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [all better] Re: regression: massive trouble with fpu rework |
| Date | 2015-06-27 11:00 +0200 |
| Message-ID | <pFU7T-OB-11@gated-at.bofh.it> (permalink) |
| References | <pFRMK-62W-1@gated-at.bofh.it> <pFTvb-5J-3@gated-at.bofh.it> <pFTER-gH-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sat, 2015-06-27 at 10:25 +0200, Ingo Molnar wrote:
> * Mike Galbraith <umgwanakikbuti@gmail.com> wrote:
>
> > On Sat, 2015-06-27 at 08:25 +0200, Mike Galbraith wrote:
> > > Hi Ingo,
> > >
> > > My i7-4790 box is having one hell of a time with this merge window, is
> > > dead in the water.
> >
> > BIOS setting "Limit CPUID Maximum" upsets new fpu code mightily.
>
> Ok, that's interesting. Mind explaining it a bit more verbosely - which setting is
> causing what?
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'.
> This would suggest sensitivity on CPUID details, i.e. that doing
> fpu__init_system() before other CPU init sequences is causing the bug.
>
> Does the patch below perhaps make a difference? (I'd suggest to apply it _without_
> the other patch I sent.)
Yup, that made it not care about the BIOS setting.. again.
> Thanks,
>
> Ingo
>
> arch/x86/kernel/cpu/common.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
> index 9fc5e3d9d9c8..922c5e0cea4c 100644
> --- a/arch/x86/kernel/cpu/common.c
> +++ b/arch/x86/kernel/cpu/common.c
> @@ -742,7 +742,6 @@ static void __init early_identify_cpu(struct cpuinfo_x86 *c)
> cpu_detect(c);
> get_cpu_vendor(c);
> get_cpu_cap(c);
> - fpu__init_system(c);
>
> if (this_cpu->c_early_init)
> this_cpu->c_early_init(c);
> @@ -754,6 +753,7 @@ static void __init early_identify_cpu(struct cpuinfo_x86 *c)
> this_cpu->c_bsp_init(c);
>
> setup_force_cpu_cap(X86_FEATURE_ALWAYS);
> + fpu__init_system(c);
> }
>
> void __init early_cpu_init(void)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[all better] Re: regression: massive trouble with fpu rework Mike Galbraith <umgwanakikbuti@gmail.com> - 2015-06-27 10:20 +0200
Re: [all better] Re: regression: massive trouble with fpu rework Ingo Molnar <mingo@kernel.org> - 2015-06-27 10:30 +0200
Re: [all better] Re: regression: massive trouble with fpu rework Mike Galbraith <umgwanakikbuti@gmail.com> - 2015-06-27 11:00 +0200
Re: [all better] Re: regression: massive trouble with fpu rework Henrique de Moraes Holschuh <hmh@hmh.eng.br> - 2015-06-27 23:10 +0200
Re: [all better] Re: regression: massive trouble with fpu rework Henrique de Moraes Holschuh <hmh@hmh.eng.br> - 2015-06-29 03:20 +0200
Re: [all better] Re: regression: massive trouble with fpu rework "H. Peter Anvin" <hpa@zytor.com> - 2015-06-30 22:30 +0200
csiph-web