commit | 6cba33580263963af9a79fb73ee88debd533991f | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Fri Feb 18 14:18:24 2022 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Feb 24 21:24:21 2022 +0000 |
tree | a04c57ec3070093022643ca802a924ea252a70a2 | |
parent | 4bc52e6aa5c3a2d0b8098afef7268cf0c97d6fd4 [diff] |
devices: pci: move PciAddress to its own file PciAddress is not really related to pci_root. Split it out so that it is easier to find and so it can have its own tests nearby. No code changes. BUG=None TEST=cargo build Change-Id: I2bdad518de76587506593292cf0fbdb6b7066c1e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3475439 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.