commit | 81b5e616d6ac54e98375605d887ffc4949516ae6 | [log] [tgz] |
---|---|---|
author | Vineeth Pillai <vineethrp@google.com> | Sat Feb 19 03:00:15 2022 +0000 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 20 18:04:21 2022 +0000 |
tree | 9e219c8be641530248e444ec3dec7511bb3bf599 | |
parent | d0b91ab0bef734cdcb14d660151a9ce008b65fce [diff] |
crosvm: vm_events: consolidate vm events into one framework. crosvm waits on events like exit, reset, crash, guest panic etc and uses eventfd to wait on these events. As of now, we have 4 eventfds and may increase. This is an attempt to consolidate all Vm events into one framework. Use Tube instead of Event to get consistent behavior between OSes. Implement a wrapper over Tube to have a consistent API for events. BUG=None. TEST=Built crosvm. Ran a minimal vm to panic and verified that crosvm received the panic event. cargo test on devices. Change-Id: I313d428de5e3ce3b879982f913918ec0a4a72c35 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3480577 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Vineeth Pillai <vineethrp@google.com> Reviewed-by: Noah Gold <nkgold@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.