x86/amd: Stop updating the Zenbleed mitigation dynamically

This was potentially helpful when the chickenbit was the only mitigation and
microcode had not been released, but that was two years ago.

Zenbleed microcode has been avaialble since December 2023, and the subsequent
Entrysign signature vulnerability means that firmware updates block OS-loading
and more OS-loadable microcode will be produced for Zen2.

i.e. the Zenbleed fix is not going to appear at runtime these days.

No practical change.

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
master commit: 5cd1ac1575
master date: 2025-11-27 18:22:20 +0000
This commit is contained in:
Andrew Cooper authored and Jan Beulich committed 2025-12-03 11:44:12 +01:00
1 parent 601bbb00d2
commit f5b36e23ec
3 files changed
+1 -5

No files matched your search

+1 -1
View File
@@ -913,7 +913,7 @@ void __init detect_zen2_null_seg_behaviour(void)
}
void amd_check_zenbleed(void)
static void amd_check_zenbleed(void)
{
const struct cpu_signature *sig = &this_cpu(cpu_sig);
unsigned int good_rev;
-2
View File
@@ -373,8 +373,6 @@ static int cf_check apply_microcode(const struct microcode_patch *patch,
"microcode: CPU%u updated from revision %#x to %#x, date = %04x-%02x-%02x\n",
cpu, old_rev, rev, patch->year, patch->month, patch->day);
amd_check_zenbleed();
return 0;
}
-2
View File
@@ -504,8 +504,6 @@ enum ap_boot_method {
};
extern enum ap_boot_method ap_boot_method;
void amd_check_zenbleed(void);
#endif /* !__ASSEMBLY__ */
#endif /* __ASM_X86_PROCESSOR_H */
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.