commit | a1fac454ed4d296a850ab9f75dbbf3e6417d5f0c | [log] [tgz] |
---|---|---|
author | Shao-Chuan Lee <shaochuan@chromium.org> | Wed Apr 13 12:12:35 2022 +0900 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 13 17:46:40 2022 +0000 |
tree | b153b8475c9ace4109ed41669c71eda5e65c8927 | |
parent | c6d01ebdbc58016d06d7d30e9cee2e929c2e7f00 [diff] |
Revert "gfxstream: support async fence cb" This reverts commit 3c2d5cefa2ade3a3339e68931f9305a8e2d17c47. Reason for revert: depends on crrev.com/c/2860746 Original change's description: > gfxstream: support async fence cb > > This adds the asynchronous interrupts in crosvm-gpu for gfxstream. > This will allow gfxstream to alternate between the main signalling > method (ASG [1]) and the more traditional interrupts when it > makes sense performance-wise. > > gfxstream also requires new write fence callbacks that take into > account the ring_idx and ctx_id where the fence is on. > > [1] goto.google.com/address-space-graphics > > BUG=b:192614792 > TEST=Tested locally with Vulkan cereal > > Change-Id: I010d9ebfc71594b393fee062b984a4c6d69404d8 > Reviewed-on: > https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3027489 > Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> > Tested-by: kokoro <noreply+kokoro@google.com> > Commit-Queue: Gurchetan Singh <gurchetansingh@chromium.org> BUG=b:192614792,b:228782431,b:228521246 TEST=arc.Notification.vm on kukui-arc-r TEST=dEQP-VK.wsi.android.swapchain.create#image_usage on dedede/kukui-arc-r Change-Id: I4d2c43320880e38e8396cee3b96ce8c32addf39b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3584075 Reviewed-by: Kazuhiro Inaba <kinaba@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Ryan Neph <ryanneph@google.com> Commit-Queue: Ryan Neph <ryanneph@google.com>
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.