RFC: bzImage / initrd support #428
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Tries loading as ELF first, then falls back to bzImage. bzImage is slower to boot than ELF, because the kernel has to decompress itself. Added an init_size field to the bootparams block, which the decompressor uses to know how much space it has to work with. Made it big enough for a moderate sized kernel. We really ought to be extracting the bootparams block from the kernel instead. Signed-off-by: Tim Deegan <tdeegan@amazon.com>
Plumb through an optional initrd path from the REST API, and load it at a fixed address. Signed-off-by: Tim Deegan <tdeegan@amazon.com>
|
You can uncompress a bzImage with extract-vmlinux and maybe use But, in general, bzImage and initrd support would be nice to have. |
|
I have rebased this but the source repo was removed, so I needed to make a new PR: #670 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I put this together for testing embedded images where I couldn't easily build my own ELF vmlinux. I'm not sure if this is something you want at all. :) I see it's explicitly not on the customer milestones and it's slower than booting an ELF because of the decompression time. If it is useful I can add some unit tests &c. If not, nbd.