| commit | 9c7fd949962dd4e5a1a64a44adc0270e77a27dc1 | [log] [tgz] |
|---|---|---|
| author | Daniel Verkamp <dverkamp@chromium.org> | Tue Dec 14 13:06:56 2021 -0800 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Dec 15 19:34:06 2021 +0000 |
| tree | 57a3ff199cb72ef6d1803b647adbbeb3d41805ac | |
| parent | 7c97b2e7d3ae6a3dd9e4ead22f02c2c8df4d78cc [diff] |
devices: usb: use anyhow to provide better errors Previously, if any event handler in the event loop failed, it would print a generic "event loop stopping due to handle event error" message and stop working. This is not particularly useful for determining which event handler actually failed. Instead of returning an empty Err, use anyhow::Context to associate each potential failure with a human-readable error string. chromium:1278424 TEST=Cause USB event loop failure, observe more useful message Change-Id: I438a96bf757946efbd03a99ef0e17dfbf0d4e1c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3339793 Reviewed-by: Dmitry Torokhov <dtor@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@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.
