On Tue, Feb 2, 2016 at 9:15 PM, Jan Engelhardt
On Tuesday 2016-02-02 18:53, Andrei Borzenkov wrote:
Am Dienstag, 2. Februar 2016, 16:18:04 CET schrieb Jan Engelhardt:
The earlycpio image contains CPU firmware updates, and since not all CPUs support that, not all systems have an early cpio image that can be skipped.
Is there any reason it cannot be part of initrd? As far as I understand, all individual parts are simply extracted by kernel onto initramfs anyway ...
"""Kernel can update microcode in early phase of boot time. Loading microcode early can fix CPU issues before they are observed during kernel boot time. [...] During BSP boot (before SMP starts), if the kernel finds the microcode file in the initrd file,
So why it cannot be in initrd file? May be I was not clear. Distinction between "early cpio" and "initrd" is significant when "initrd" is not itself initramfs image. But dracut does create initramfs image which is unpacked into initramfs. There is no difference from "early cpio" - both are unpacked in one pass. So I still miss explanation why it must be separate archive except for legacy reasons.
it parses the microcode and saves matching microcode in memory. If matching microcode is found, it will be uploaded in BSP and later on in all APs.[auxiliary processors]""" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org