mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-06 02:25:23 +00:00
4257919fa7
Launching a VVU device requires access to /dev/vfio/$vfio_group. The permissions on those files can't be set by upstart, since the files don't exist until a vvu device process binds its vvu pci device to vfio-pci. Instead, the permissions are set via udev rules. Unfortunately, there is no good way to wait for udev to modify the permissions, so the device process just needs to poll until it is successfully able to open its device. BUG=b:222424090 TEST=vmc start termina Change-Id: Id8668c66ff7ddaa7bb43061979ead51d12cde8f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3574422 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: David Stevens <stevensd@chromium.org> |
||
---|---|---|
.. | ||
src | ||
Cargo.toml |