commit | 339b7b680174fc280a4d106a35fd3e82270f4b6b | [log] [tgz] |
---|---|---|
author | Alexandre Courbot <acourbot@chromium.org> | Tue Dec 28 16:05:01 2021 +0900 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Jan 12 07:58:53 2022 +0000 |
tree | b40e340828f4d57ab857ae18028de916de354dc8 | |
parent | 5a250fcb263790b2d4113e352d46f60a93140eff [diff] |
virtio: video: rename UnresolvedGuestResource to UnresolvedResourceEntry The current naming is a bit confusing: a resource is one or several buffers that are each made of one or several entries. The elements that we return to the device are thus resource entries (that need to be resolved into a single resource) and not the whole resources themselves. BUG=b:209523781 TEST=cargo build --features "video-decoder,video-encoder" Change-Id: Ie3d89c48f9b3e7758b455ea1b2d4954daf248d0c Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3379628 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: 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 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.