diff options
| author | Daniel Verkamp <dverkamp@chromium.org> | 2019-05-13 12:34:54 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2019-05-14 23:57:41 -0700 |
| commit | 050af40382a5619278fc08eef7dfbde5591abd76 (patch) | |
| tree | c8f4284dbe5b59e91b0f66b9466519cfeeccad24 /kokoro/README.md | |
| parent | 21accb31ac9056ab28930689ddd9dce185956258 (diff) | |
| download | crosvm-050af40382a5619278fc08eef7dfbde5591abd76.tar crosvm-050af40382a5619278fc08eef7dfbde5591abd76.tar.gz crosvm-050af40382a5619278fc08eef7dfbde5591abd76.tar.bz2 crosvm-050af40382a5619278fc08eef7dfbde5591abd76.tar.lz crosvm-050af40382a5619278fc08eef7dfbde5591abd76.tar.xz crosvm-050af40382a5619278fc08eef7dfbde5591abd76.tar.zst crosvm-050af40382a5619278fc08eef7dfbde5591abd76.zip | |
x86_64: support loading bzImage kernels
The current kernel loader expects an extracted ELF kernel; this adds complexity to the build and test process for the guest kernel, since the normal output of a Linux kernel build is a bzImage-format kernel. bzImage also supports compressed kernels, which are smaller on disk and potentially quicker to load, depending on disk and CPU speed. Add support for loading of bzImage-format kernels, and use the 64-bit boot protocol as described in the official Linux/x86 boot protocol: https://www.kernel.org/doc/Documentation/x86/boot.txt The existing ELF loader is kept for compatibility with shipping kernel images; if a kernel image doesn't have the ELF signature, it is passed to the bzImage loader as a fallback. BUG=None TEST=Boot bzImage and extracted ELF kernels on x86-64 Change-Id: I90be4cd597d15bc89e63f0f6cbc781c5c8c2eaeb Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1609969 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Dylan Reid <dgreid@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
Diffstat (limited to 'kokoro/README.md')
0 files changed, 0 insertions, 0 deletions