summaryrefslogtreecommitdiffstats
path: root/Documentation/x86
diff options
context:
space:
mode:
authorIngo Molnar <mingo@kernel.org>2015-06-27 10:25:14 +0200
committerIngo Molnar <mingo@kernel.org>2015-06-30 07:22:10 +0200
commitdb52ef74b35dcb91fd154fa52c618bdd1b90e28e (patch)
tree716b19ac29c431ae50ef447a4fc2797e0e5f43e0 /Documentation/x86
parent407a2c720556e8e340e06f6a7174f5d6d80cf9ea (diff)
downloadop-kernel-dev-db52ef74b35dcb91fd154fa52c618bdd1b90e28e.zip
op-kernel-dev-db52ef74b35dcb91fd154fa52c618bdd1b90e28e.tar.gz
x86/fpu: Fix FPU related boot regression when CPUID masking BIOS feature is enabled
Mike Galbraith reported: " My i7-4790 box is having one hell of a time with this merge window, dead in the water. BIOS setting "Limit CPUID Maximum" upsets new fpu code mightily. " It turns out that Linux does a double workaround here, as per: 066941bd4eeb ("x86: unmask CPUID levels on Intel CPUs") it undoes the BIOS workaround - but as a side effect the CPUID state is not completely constant during early init anymore, and the new FPU init code did not take this into account. So what happened is that the xstate init code did not have full CPUID available, which broke subsequent attempts to use xstate features. Fix this by ordering the early FPU init code to after we've stabilized the CPUID state. Reported-bisected-and-tested-by: Mike Galbraith <umgwanakikbuti@gmail.com> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Borislav Petkov <bp@alien8.de> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Mike Galbraith <umgwanakikbuti@gmail.com> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/20150627082514.GA10894@gmail.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'Documentation/x86')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud