commit | dbba029d13acd080f604470fac0a929b29126ec2 | [log] [tgz] |
---|---|---|
author | Haiwei Li <haiwei.li@intel.corp-partner.google.com> | Thu Feb 17 13:53:29 2022 +0800 |
committer | Commit Bot <commit-bot@chromium.org> | Sat Mar 05 00:24:13 2022 +0000 |
tree | 9e4bd13059d09d3dd95d16bb821a9d724e1eebe0 | |
parent | 0ae13d221e01afe75638f4afcb5cc586e34d21b3 [diff] |
devices: virtio: iommu: add socket between main process and virtio-iommu A tube channel is needed for the communication between main process and virtio-iommu worker thread, e.g. passing a vfio container file descriptor of a hot-pluggable device to the virtio-iommu backend which is in charge of the mapping/unmapping for the endpoint. BUG=b:185084350 TEST=Boot a guest with no error Change-Id: Ib5061e795227040ca400bc9a92df84a27cd26438 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3301703 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> 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.