commit | cbcfd9c8e7ffbe9687792bb342d5dd86364d040e | [log] [tgz] |
---|---|---|
author | Gurchetan Singh <gurchetansingh@chromium.org> | Thu Jul 20 16:41:55 2023 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 25 01:04:45 2023 +0000 |
tree | a7bc1f301ecf00886b16e8605c8aa4d282f31a9c | |
parent | 1258f463d4bcc5e3a4efa002644291583ad027ff [diff] |
rutabaga_gfx: renderer_utils cleanups 1) VirglCookie --> RutabagaCookie Most accurately, since gfxstream uses the cookie as well, it is neither a virgl cookie or a gfxstream cookie. It, in fact, is a rutabaga cookie. 2) Organize callbacks into gfxstream and virglrenderer files They both have *slightly* different function signatures anyways. BUG=b:292548160 TEST=compile Change-Id: I915ec747d29fe6c2d92b58ff2088009a4dfdeb29 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4712925 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com> 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 ChromeOS 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 ChromeOS devices.