On Mon, Apr 01, 2019 at 11:19:19AM +0100, Sergey Dyasli wrote:
>On 25/03/2019 17:08, Jan Beulich wrote:
> On 25.03.19 at 12:12, wrote:
>>> Currently cpu_sig struct is not updated during boot when either:
>>>
>>> 1. ucode_scan is set to false (e.g. no "ucode=scan" in cmdline)
>>> 2. ini
On 25/03/2019 17:08, Jan Beulich wrote:
On 25.03.19 at 12:12, wrote:
>> Currently cpu_sig struct is not updated during boot when either:
>>
>> 1. ucode_scan is set to false (e.g. no "ucode=scan" in cmdline)
>> 2. initrd does not contain a microcode blob
>
> What about "ucode="?
Yes,
>>> On 25.03.19 at 12:12, wrote:
> Currently cpu_sig struct is not updated during boot when either:
>
> 1. ucode_scan is set to false (e.g. no "ucode=scan" in cmdline)
> 2. initrd does not contain a microcode blob
What about "ucode="?
> These will result in cpu_sig.rev being 0 which aff
On Mon, Mar 25, 2019 at 11:12:17AM +, Sergey Dyasli wrote:
>Currently cpu_sig struct is not updated during boot when either:
>
>1. ucode_scan is set to false (e.g. no "ucode=scan" in cmdline)
>2. initrd does not contain a microcode blob
>
>These will result in cpu_sig.rev being 0 which
Currently cpu_sig struct is not updated during boot when either:
1. ucode_scan is set to false (e.g. no "ucode=scan" in cmdline)
2. initrd does not contain a microcode blob
These will result in cpu_sig.rev being 0 which affects APIC's
check_deadline_errata() and retpoline_safe() functions
