diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2015-08-22 14:41:17 (GMT) |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2015-08-22 15:01:48 (GMT) |
commit | a57e456a7b28431b55e407e5ab78ebd5b378d19e (patch) | |
tree | 3e0755f715e8f34ac6f642d55eb9b02c02a4faf9 /arch/arc/Kbuild | |
parent | 827409b2f5b58573ae3774fe6bd2d6daeb335878 (diff) | |
download | linux-a57e456a7b28431b55e407e5ab78ebd5b378d19e.tar.xz |
x86/apic: Fix fallout from x2apic cleanup
In the recent x2apic cleanup I got two things really wrong:
1) The safety check in __disable_x2apic which allows the function to
be called unconditionally is backwards. The check is there to
prevent access to the apic MSR in case that the machine has no
apic. Though right now it returns if the machine has an apic and
therefor the disabling of x2apic is never invoked.
2) x2apic_disable() sets x2apic_mode to 0 after registering the local
apic. That's wrong, because register_lapic_address() checks x2apic
mode and therefor takes the wrong code path.
This results in boot failures on machines with x2apic preenabled by
BIOS and can also lead to an fatal MSR access on machines without
apic.
The solutions are simple:
1) Correct the sanity check for apic availability
2) Clear x2apic_mode _before_ calling register_lapic_address()
Fixes: 659006bf3ae3 'x86/x2apic: Split enable and setup function'
Reported-and-tested-by: Javier Monteagudo <javiermon@gmail.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://bugzilla.redhat.com/show_bug.cgi?id=1224764
Cc: stable@vger.kernel.org # 4.0+
Cc: Laura Abbott <labbott@redhat.com>
Cc: Jiang Liu <jiang.liu@linux.intel.com>
Cc: Joerg Roedel <joro@8bytes.org>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Borislav Petkov <bp@alien8.de>
Diffstat (limited to 'arch/arc/Kbuild')
0 files changed, 0 insertions, 0 deletions