commit | cd75771ea8dac7704b0e7b840ededcff7c1fce9e | [log] [tgz] |
---|---|---|
author | Peter Fang <peter.fang@intel.corp-partner.google.com> | Mon Dec 20 03:46:59 2021 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Mar 10 16:59:23 2022 +0000 |
tree | aa739daca975ed8f6b7d4e7ae5fb326714844d01 | |
parent | 3fbf6c21fdc994e4f78b34a82006cb44eed43260 [diff] |
x86_64: acpi: always use virtual reset register Always advertise support for ACPI reset register, regardless of FADT forwarding. The current reset register points to the PCI reset register (CF9), which is always virtualized. The Linux x86 kernel prioritizes using the ACPI reset register in its reboot flow. BUG=b:199383670 TEST=boot Linux kernel and reboot Change-Id: Ib644e1062eb6e040d16c0c8d7cec2a54a86b3918 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3350495 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Junichi Uekawa <uekawa@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Tomasz Nowicki <tnowicki@google.com>
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.