mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-11-24 20:48:55 +00:00
49a6c3cf2d
On aarch64, we load BIOS payloads at offset 0x200000 because cuttlefish's u-boot BIOS requires the FDT at offset zero. However, in a separate use case, we are loading BIOS payloads that are OK with dynamic FDT addresses, but might use the Gunyah hypervisor, which currently requires the payload to be loaded at offset zero. One algorithm can't satisfy both. Both the u-boot setup and Gunyah ought to be made more flexible, but it seems useful to make crosvm's behavior configurable. It lets us adjust those use cases eventually without causing an immediate backwards incompatability scramble. A new "after-payload" mode is included that matches crosvm's RISCV FDT address behavior and potentially helps with the TODO for >4GB VMs. BUG=b:353758405 Change-Id: I886f47cf8e0a6b02218794615215a0e972a4ace2 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5740018 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Frederick Mayle <fmayle@google.com> |
||
|---|---|---|
| .. | ||
| src | ||
| bindgen.sh | ||
| Cargo.toml | ||