mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-06 10:32:10 +00:00
No description
69c8d8093d
At present the VVU PCI driver writes the feature bits it wants to enable to the device feature bits first, and then reads the device feature bits in the initialization sequence. However, the correct sequence is reading the device feature bits first, and writing the feature bits to enable to the driver feature bits next. This incorrect initialization sequence causes warning messages when you run the VVU driver. Fix the driver so that it follows the correct feature bits initialization sequence. BUG=b:216752120 TEST=VVU block device works with no warning message. TEST=presubmit --quick Change-Id: I7f7536143ee2a037fd71aa216513ad732b407cc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3705077 Commit-Queue: Takaya Saeki <takayas@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> |
||
|---|---|---|
| .cargo | ||
| .devcontainer | ||
| .github | ||
| aarch64 | ||
| acpi_tables | ||
| arch | ||
| argh_helpers | ||
| base | ||
| bin | ||
| bit_field | ||
| broker_ipc | ||
| ci/kokoro | ||
| common | ||
| cros_async | ||
| crosvm-fuzz | ||
| crosvm_control | ||
| crosvm_plugin | ||
| devices | ||
| disk | ||
| docs/book | ||
| fuse | ||
| gpu_display | ||
| hypervisor | ||
| infra | ||
| integration_tests | ||
| io_uring | ||
| kernel_cmdline | ||
| kernel_loader | ||
| kvm | ||
| kvm_sys | ||
| libcras_stub | ||
| linux_input_sys | ||
| logo | ||
| media | ||
| metrics | ||
| net_sys | ||
| net_util | ||
| power_monitor | ||
| protos | ||
| qcow_utils | ||
| resources | ||
| rutabaga_gfx | ||
| seccomp | ||
| serde_keyvalue | ||
| src | ||
| system_api_stub | ||
| 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 | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| navbar.md | ||
| OWNERS | ||
| PRESUBMIT.cfg | ||
| README.chromeos.md | ||
| README.md | ||
| run_tests | ||
| rust-toolchain | ||
| setup_cros_cargo.sh | ||
| test_all | ||
| unblocked_terms.txt | ||
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.
- Issue tracker
