commit | 0c8a924bd7c6bfe67fe3c74e9331d7252fa7c0d2 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Tue Jan 02 14:03:45 2024 -0800 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 03 18:20:56 2024 +0000 |
tree | edb8f4994969efbc5be1a929afc9c62a64a3b765 | |
parent | b535b87cd70911691caaf59a08bb7e4c618b811c [diff] |
devices: virtio: fully spell out video DeviceTypes Rename the virtio-video device types to match the desired serde-derived names for consistency: - DeviceType::VideoDec -> DeviceType::VideoDecoder - DeviceType::VideoEnc -> DeviceType::VideoEncoder Change-Id: I5b9b001d5b34b799086585eb084fa43857b1c32d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5160256 Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Alexandre Courbot <acourbot@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.