commit | c206d1a3d498431c2c4106e5ebf7436339be1e1c | [log] [tgz] |
---|---|---|
author | David Stevens <stevensd@chromium.org> | Wed Jun 29 12:34:46 2022 +0900 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 13 01:50:54 2022 +0000 |
tree | 6417b51503f5232ca7f72cd82f847fc194b7a07d | |
parent | 92fabf70b810c5a847f01598b648ea5ec1ac2765 [diff] |
devices: iommu: replace memory_mapper::Error with anyhow Replace thiserror enum with anyhow. The only error that needs to be checked for is IovaPartialOverlap, which can be handled by changing the add/remove map return types from () to bool. This CL also adds proper handling of that case to the iommu device. BUG=b:237620529 TEST=compiles Change-Id: I066cf2d609d1264b235b019ec098f9a761535f9a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3737405 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: David Stevens <stevensd@chromium.org> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Tested-by: kokoro <noreply+kokoro@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 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.