Frederick Mayle 26d841e626 crosvm: create guest memory layout after hypervisor ... No behavior change intended. We'd like to make some aspects of the guest memory layout dependent on hypervisor capabilities in future commits. Note for x86_64: `Arch::guest_memory_layout` initializes some global state so some care is needed when moving it relative to other code. In this case it is safe because the only code being moved before `Arch::guest_memory_layout` is `get_default_hypervisor`, which is currently a constant, and `Kvm::new_with_path`, which just performs an `open` syscall and wraps it in a `Kvm` struct. Neither depend on the x86_64 specific global state. BUG=b:232360323,b:244630071 Change-Id: I8bf70bb18e56dd7e7ac78c615fdb9877a87b66c4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4197000 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Vaibhav Nagarnaik <vnagarnaik@google.com>		2023-02-01 00:05:48 +00:00
..
src	crosvm: create guest memory layout after hypervisor	2023-02-01 00:05:48 +00:00
.build_test_skip	build_test: misc options, improvements, amd bug fixes	2020-10-15 13:40:32 +00:00
Cargo.toml	aarch64: switch rng seed generation to rand crate	2023-01-13 23:43:44 +00:00