summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorBorislav Petkov <bp@suse.de>2019-06-13 15:49:02 +0200
committerBorislav Petkov <bp@suse.de>2019-06-15 10:00:29 +0200
commit78f4e932f7760d965fb1569025d1576ab77557c5 (patch)
treece347a9bb7228f89683c7fe9a2c8ebe2589aba5d /crypto
parentf3176ec9420de0c385023afa3e4970129444ac2f (diff)
downloadlinux-78f4e932f7760d965fb1569025d1576ab77557c5.tar.gz
linux-78f4e932f7760d965fb1569025d1576ab77557c5.tar.bz2
linux-78f4e932f7760d965fb1569025d1576ab77557c5.zip
x86/microcode, cpuhotplug: Add a microcode loader CPU hotplug callback
Adric Blake reported the following warning during suspend-resume: Enabling non-boot CPUs ... x86: Booting SMP configuration: smpboot: Booting Node 0 Processor 1 APIC 0x2 unchecked MSR access error: WRMSR to 0x10f (tried to write 0x0000000000000000) \ at rIP: 0xffffffff8d267924 (native_write_msr+0x4/0x20) Call Trace: intel_set_tfa intel_pmu_cpu_starting ? x86_pmu_dead_cpu x86_pmu_starting_cpu cpuhp_invoke_callback ? _raw_spin_lock_irqsave notify_cpu_starting start_secondary secondary_startup_64 microcode: sig=0x806ea, pf=0x80, revision=0x96 microcode: updated to revision 0xb4, date = 2019-04-01 CPU1 is up The MSR in question is MSR_TFA_RTM_FORCE_ABORT and that MSR is emulated by microcode. The log above shows that the microcode loader callback happens after the PMU restoration, leading to the conjecture that because the microcode hasn't been updated yet, that MSR is not present yet, leading to the #GP. Add a microcode loader-specific hotplug vector which comes before the PERF vectors and thus executes earlier and makes sure the MSR is present. Fixes: 400816f60c54 ("perf/x86/intel: Implement support for TSX Force Abort") Reported-by: Adric Blake <promarbler14@gmail.com> Signed-off-by: Borislav Petkov <bp@suse.de> Reviewed-by: Thomas Gleixner <tglx@linutronix.de> Cc: Peter Zijlstra <peterz@infradead.org> Cc: <stable@vger.kernel.org> Cc: x86@kernel.org Link: https://bugzilla.kernel.org/show_bug.cgi?id=203637
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions