From: Suravee Suthikulpanit <suravee.suthikulpa...@amd.com>
On AMD family15h, applying microcode patch on the a core (core0)
would also affect the other core (core1) in the same compute unit.
The driver would skip applying the patch on core1, but it still
need to update kernel structures to reflect the proper patch level.
The current logic is not updating the struct ucode_cpu_info.cpu_sig.rev
of the skipped core. This causes the
/sys/devices/system/cpu/cpu1/microcode/version
to report incorrect patch level as shown below:
[ 10.708841] microcode: CPU0: new patch_level=0x0600063d
[ 10.714256] microcode: CPU1: patch_level=0x06000626
[ 10.719345] microcode: CPU2: patch_level=0x06000626
[ 10.748095] microcode: CPU2: new patch_level=0x0600063d
[ 10.753365] microcode: CPU3: patch_level=0x06000626
[ 10.758264] microcode: CPU4: patch_level=0x06000626
[ 10.786999] microcode: CPU4: new patch_level=0x0600063d
Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpa...@amd.com>
---
arch/x86/kernel/microcode_amd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/kernel/microcode_amd.c b/arch/x86/kernel/microcode_amd.c
index 7123b5d..af99f71 100644
--- a/arch/x86/kernel/microcode_amd.c
+++ b/arch/x86/kernel/microcode_amd.c
@@ -216,6 +216,7 @@ int apply_microcode_amd(int cpu)
/* need to apply patch? */
if (rev >= mc_amd->hdr.patch_id) {
c->microcode = rev;
+ uci->cpu_sig.rev = rev;
return 0;
}
--
1.8.1.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
