commit | a1a57460a3ad2541982600f011cd13d34fadb9a9 | [log] [tgz] |
---|---|---|
author | Peter Fang <peter.fang@intel.corp-partner.google.com> | Thu Jul 14 01:01:11 2022 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 17 11:20:34 2022 +0000 |
tree | 8fb30cb3ae36af4051a15debd2d04acfba4085ae | |
parent | 379dd2dfecf1a0c06adf0f6e257a5ebc75374cb8 [diff] |
devices: vfio_pci: identify intel-lpss devices via cmdline intel-lpss devices need special handling during BAR accesses due to PV operations in the guest (when compiled with the direct feature). Allow identification of such devices via a new vfio parameter, intel-lpss, so that it can tag them for PV handling. BUG=b:232887201 TEST=crosvm accepts the intel-lpss parameter in --vfio Change-Id: I6ce710b112e7d286e43014d7dc55ec4e68939731 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3764936 Tested-by: Peter Fang <peter.fang@intel.corp-partner.google.com> Commit-Queue: Tomasz Nowicki <tnowicki@google.com> Reviewed-by: 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.