commit | a4a46df15e7ced0d52dd3f42ef391c8b7064a279 | [log] [tgz] |
---|---|---|
author | David Stevens <stevensd@chromium.org> | Fri Jun 17 17:30:25 2022 +0900 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 17 09:15:19 2022 +0000 |
tree | a7e6fca588d943cefb21873fb82126ea71d4197b | |
parent | 89479b41dbd39b9c87b5d93e88971c5615ee73d1 [diff] |
x86_64: fix e820 computation Exclude pci mmio region below 4gb from the e820 table. This is a followup to CL:3696671. BUG=None TEST=arc.Boot.vm Change-Id: I07c2b9a9e2e4e27682c4b60406625b019eea195f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3708390 Reviewed-by: Junichi Uekawa <uekawa@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: David Stevens <stevensd@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.