commit | 6f576dd81388a4eaa1f11463f3a877c75730bf36 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Wed Jun 29 21:32:53 2022 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 07 23:24:05 2022 |
tree | c7d213666ddabafe5e8f039287d105f98299afdd | |
parent | 814114c64cf1e75b958c9c478969e8c63e58570d [diff] |
hypervisor: x86_64: default Regs::rip to reset vector This matches the reset value of the registers defined by the Intel manuals. It is currently overwritten on all paths initializing Regs, but it will be used in an upcoming commit to simplify the BIOS boot path. BUG=b:237095693 TEST=Boot x86_64 Linux TEST=cargo test -p x86_64 Change-Id: I7a96882fad05440c98bde2fad7ad15c0890f1cfa Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3735639 Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the Chrome OS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.
crosvm is currently used to run Linux/Android guests on Chrome OS devices.