summaryrefslogtreecommitdiff
path: root/scripts/kconfig/tests/conditional_dep/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorSohil Mehta <sohil.mehta@intel.com>2026-05-28 11:48:25 -0700
committerBorislav Petkov (AMD) <bp@alien8.de>2026-05-28 18:41:32 -0700
commit87a451161f36a34307ca09aaa66f233d68642b5f (patch)
tree8128bceafb3b2f223f742aaa0a7f65fb9f336ec8 /scripts/kconfig/tests/conditional_dep/git@git.tavy.me:linux.git
parentdedcf8e104414f2e5517c2f9abad4bd31fd5d8e2 (diff)
x86/cpu: Fix a F00F bug warning and clean up surrounding code
On x86 SMP systems with the F00F bug present, do_clear_cpu_cap() rightfully warns that the code clears the X86_BUG_F00F flag after alternatives have been patched. X86_BUG_F00F is first cleared in intel_workarounds() and then set for the affected models. This sequence works fine on the BSP but on AP bringup, where alternatives have already been patched and clearing the flag there triggers the warning. There is no technical reason for clearing the flag before setting it. It is mainly an artifact of introducing the X86_BUG_F00F flag in e2604b49e8a8 ("x86, cpu: Convert F00F bug detection"). Remove the unnecessary clearing of the flag. While at it, remove the kernel notification and the surrounding logic to inform the user about the workaround exactly once. If needed, the presence of the F00F bug can be determined through /proc/cpuinfo. Additionally, the F00F bug was the last remaining user of clear_cpu_bug(). With no users left, get rid of this helper as well. [ bp: Massage commit message. ] Co-developed-by: Richard Weinberger <richard@nod.at> Signed-off-by: Richard Weinberger <richard@nod.at> Signed-off-by: Sohil Mehta <sohil.mehta@intel.com> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de> Reviewed-by: Ahmed S. Darwish <darwi@linutronix.de> Link: https://patch.msgid.link/20260528184826.3642051-1-sohil.mehta@intel.com
Diffstat (limited to 'scripts/kconfig/tests/conditional_dep/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions