commit | bfe3bcf96a7f4d859c81a4da86d141075d56b284 | [log] [tgz] |
---|---|---|
author | Ryan Neph <ryanneph@google.com> | Thu Feb 10 14:09:51 2022 -0800 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 19 22:39:47 2022 +0000 |
tree | fb31a0590916ea115972028fc45b7c423b04df5a | |
parent | 30074cb73475a8ef6ebffba5a7586af4e1dd169a [diff] |
rutabaga_gfx: virglrenderer: add support for per-context fencing Permits virglrenderer contexts to make use of per-context/per-ring fencing. BUG=b:175527587 BUG=b:193892617 TEST=cargo build --features=virgl_renderer,virgl_renderer_next,gfxstream TEST=Run glxgears and vkcube in a crosvm guest VM with virglrenderer Cq-Depend: chromium:3654708 Change-Id: I30028afa5daff2a7a1b0ade13bc9fae2cd548f8d Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3628302 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Gurchetan Singh <gurchetansingh@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.