Re: [Xen-devel] [PATCH v1 for 4.13] x86/microcode: refuse to load the same revision ucode

[Jan Beulich <jbeulich@xxxxxxxx>]

On 22.11.2019 11:52, Sergey Dyasli wrote:
> Currently if a user tries to live-load the same ucode revision that CPU
> already has, he will get a single message in Xen log like:
> 
>     (XEN) 128 cores are to update their microcode
> 
> No actual ucode loading will happen and this situation can be quite
> confusing. Fix this by starting ucode update only when a newer ucode
> revision has been provided. This is based on an assumption that all CPUs
> in the system have the same ucode revision. If that's not the case,
> the system must be considered unstable.

Unstable or not, I did specifically convince Chao to handle such
systems, bringing them into better shape. I can only repeat that
I actually have a system where on each socket firmware loads ucode
only on the first core. I don't see why boot time loading and late
loading should differ in behavior for such a system.

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel