diff options
| author | Daniel Verkamp <dverkamp@chromium.org> | 2019-05-17 10:55:45 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2019-05-20 15:47:23 -0700 |
| commit | 3007ff3cf408f9e6a2e0731a4fa7d6f8f65dfa47 (patch) | |
| tree | 339cc27c92c02bb818f4d30550ba090ddd020e19 /src/main.rs | |
| parent | be1ad40a0e698a0b6c483d0162cd80df6ce78ed8 (diff) | |
| download | crosvm-3007ff3cf408f9e6a2e0731a4fa7d6f8f65dfa47.tar crosvm-3007ff3cf408f9e6a2e0731a4fa7d6f8f65dfa47.tar.gz crosvm-3007ff3cf408f9e6a2e0731a4fa7d6f8f65dfa47.tar.bz2 crosvm-3007ff3cf408f9e6a2e0731a4fa7d6f8f65dfa47.tar.lz crosvm-3007ff3cf408f9e6a2e0731a4fa7d6f8f65dfa47.tar.xz crosvm-3007ff3cf408f9e6a2e0731a4fa7d6f8f65dfa47.tar.zst crosvm-3007ff3cf408f9e6a2e0731a4fa7d6f8f65dfa47.zip | |
x86_64: load initrd at max address
This matches behavior of other bootloaders (grub2, iPXE), and the kernel seems to be relying on this; decompression of the initrd fails if the initrd is loaded right after the kernel as before, but succeeds if loaded at the maximum address. BUG=None TEST=Boot Debian kernel + initrd on workstation Change-Id: If7712efb05f55ef413a419dfe276ed3f68c335b7 Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1616989 Tested-by: kokoro <noreply+kokoro@google.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org>
Diffstat (limited to 'src/main.rs')
0 files changed, 0 insertions, 0 deletions