Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

early microcode (firmware) should not be compressed #27

Open
smoser opened this issue May 1, 2023 · 0 comments
Open

early microcode (firmware) should not be compressed #27

smoser opened this issue May 1, 2023 · 0 comments

Comments

@smoser
Copy link
Collaborator

smoser commented May 1, 2023

tldr; the early microcode portion of an initramfs (/firmware) should be not be compressed.

When creating an initramfs, bootkit is currently creating a single cpio archive by combining uncompressed multiple cpio archives and then compressing the set of them. Note that doing it this way means that there are multiple end records. That seems not to bother the kernel.

So we end up with one cpio archive that has /firmware and all the other files. firmware portion of that is "early microcode".

Per Documentation/arch/x86/microcode.rst the /firmware bits are :

The format of the combined initrd image is microcode in (uncompressed) cpio format followed by the (possibly compressed) initrd image. The loader parses the combined initrd image during boot.

That is how both mkinitramfs and dracut create theirs.

@smoser smoser changed the title microcode (firmware) should not be compressed early microcode (firmware) should not be compressed May 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant