David Stevens add16addf4 devices: virtio: support sharing fences ... This change adds support for exporting virtio_gpu fences into virtio_wl. Without support for sending fences over virtio_wl, ARCVM must wait in the guest for fences to be signaled before sending the corresponding buffers to the host compositor. Under normal composition, it is relatively rare for fences to be unsignaled when they need to be sent over virtio_wl, although it does still happen at the far tail end. If ARCVM falls back to client composition, without this change ARCVM needs to wait on average 5-15ms (depending on how heavyweight the app's rendering is) for fences to be signaled. Support for sending fences over virtio_wl allows this extra latency to be hidden. BUG=b:136129939 TEST=Run YouTube+Play Store+graphics benchmarks simultaneously in ARCVM, with and without client composition. Change-Id: Ic7f57069c4171104c497aee6721c5c93dc6bafa4 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2363512 Tested-by: David Stevens <stevensd@chromium.org> Commit-Queue: David Stevens <stevensd@chromium.org> Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org>		2020-12-03 04:57:57 +00:00
..
src	devices: virtio: support sharing fences	2020-12-03 04:57:57 +00:00
Cargo.toml	Add "base" crate and transition crosvm usages to it from sys_util	2020-08-06 18:19:44 +00:00