mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-11-25 13:23:08 +00:00
No description
c64f5c984a
Virglrenderer interprets flag fences differently from crosvm, but this path hasn't been used until the upcoming support for multiple timelines in Venus. Virglrenderer's render_server assumes that only VIRGL_RENDERER_FENCE_FLAG_MERGEABLE is set, but before this CL, we mistakenly pass (RUTABAGA_FLAG_FENCE | RUTABAGA_FLAG_INFO_RING_IDX), which match the similarly named VIRTIO_GPU_* flags passed by the guest virtio-gpu kernel driver. Then render_server blows up... BUG=b:258854534 TEST=vkcube in VM after supporting Venus multiple timelines Change-Id: I778d9767882aaf820fb7c8cdd9d37dab75fefcf0 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4024080 Reviewed-by: Yiwei Zhang <zzyiwei@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Ryan Neph <ryanneph@google.com> |
||
|---|---|---|
| .cargo | ||
| .devcontainer | ||
| .github | ||
| .vscode | ||
| aarch64 | ||
| acpi_tables | ||
| anti_tamper | ||
| arch | ||
| argh_helpers | ||
| base | ||
| bit_field | ||
| broker_ipc | ||
| common | ||
| crash_report | ||
| cros_async | ||
| cros_fdt | ||
| cros_tracing | ||
| crosvm-fuzz | ||
| crosvm_cli | ||
| crosvm_control | ||
| crosvm_plugin | ||
| devices | ||
| disk | ||
| docs/book | ||
| e2e_tests | ||
| fuse | ||
| gpu_display | ||
| hypervisor | ||
| infra | ||
| io_uring | ||
| kernel_cmdline | ||
| kernel_loader | ||
| kvm | ||
| kvm_sys | ||
| libcras_stub | ||
| linux_input_sys | ||
| logo | ||
| media | ||
| metrics | ||
| net_sys | ||
| net_util | ||
| power_monitor | ||
| prebuilts | ||
| proto_build_tools | ||
| protos | ||
| qcow_utils | ||
| resources | ||
| rutabaga_gfx | ||
| sandbox | ||
| seccomp | ||
| serde_keyvalue | ||
| src | ||
| swap | ||
| system_api | ||
| tests | ||
| third_party | ||
| tools | ||
| tpm2 | ||
| tpm2-sys | ||
| tube_transporter | ||
| usb_sys | ||
| usb_util | ||
| vfio_sys | ||
| vhost | ||
| virtio_sys | ||
| vm_control | ||
| vm_memory | ||
| win_audio | ||
| win_util | ||
| x86_64 | ||
| .dockerignore | ||
| .gitignore | ||
| .gitmodules | ||
| .rustfmt.toml | ||
| ARCHITECTURE.md | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| DIR_METADATA | ||
| LICENSE | ||
| mypy.ini | ||
| OWNERS | ||
| PRESUBMIT.cfg | ||
| pyproject.toml | ||
| README.chromeos.md | ||
| README.md | ||
| rust-toolchain | ||
crosvm - The Chrome OS Virtual Machine Monitor
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.
- Documentation
- Announcements
- Developer Mailing List
- #crosvm on matrix.org
- Source code
- API doc, useful for searching API.
- For contribution, see the contributor guide. Mirror repository is available at GitHub for your convenience, but we don't accept bug reports or pull requests there.
- Public issue tracker
- For Googlers: See go/crosvm#filing-bugs.
