commit | 93d6c48ebb505961ee71a6aa914f1bd464865868 | [log] [tgz] |
---|---|---|
author | Federico 'Morg' Pareschi <morg@google.com> | Thu Sep 14 12:05:58 2023 +0000 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 19 07:30:26 2023 +0000 |
tree | 727c33f4131419b3de4ddb11ddea5d796e87ae2c | |
parent | 8bb6225d338f86f2957184e9953ce330f52419ba [diff] |
devices: usb: refactor backend device provider This CL splits the logic of a generic backend device provider with the specific implementation of a host backend device provider (backed by usbdevfs semantics). By separating common logic with backend-specific implementation logic, we make it easier to implement alternative backends (like virtual USB devices) in the future. BUG=b:297957754 TEST=presumit Change-Id: I1f38708cb7aefd324977e72f3f38da6f37b31213 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4865911 Commit-Queue: Morg <morg@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Ryuichiro Chiba <chibar@chromium.org> Auto-Submit: Morg <morg@google.com>
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.