Re: [PATCH] x86/microcode/intel: Check microcode revision before updating sibling threads

2018-02-18 Thread Ingo Molnar
* Raj, Ashok wrote: > Hi Ingo > > On Sat, Feb 17, 2018 at 08:50:53AM +0100, Ingo Molnar wrote: > > > > Also, more fundamentally, during microcode early testing, isn't it possible > > for > > internal iterations of the microcode to have the same revision, but be > > different? > > Atleast w

Re: [PATCH] x86/microcode/intel: Check microcode revision before updating sibling threads

2018-02-17 Thread Raj, Ashok
Hi Ingo On Sat, Feb 17, 2018 at 08:50:53AM +0100, Ingo Molnar wrote: > > Also, more fundamentally, during microcode early testing, isn't it possible > for > internal iterations of the microcode to have the same revision, but be > different? Atleast we don't do that here. Such debug microcode

Re: [PATCH] x86/microcode/intel: Check microcode revision before updating sibling threads

2018-02-16 Thread Ingo Molnar
* Ashok Raj wrote: > After updating microcode on one of the threads in the core, the > thread sibling automatically gets the update since the microcode > resources are shared. Check the ucode revision on the cpu before > performing a ucode update. s/cpu/CPU > > Signed-off-by: Ashok Raj > Cc:

[PATCH] x86/microcode/intel: Check microcode revision before updating sibling threads

2018-02-16 Thread Ashok Raj
After updating microcode on one of the threads in the core, the thread sibling automatically gets the update since the microcode resources are shared. Check the ucode revision on the cpu before performing a ucode update. Signed-off-by: Ashok Raj Cc: X86 ML Cc: LKML --- arch/x86/kernel/cpu/micr