commit | 13313d403ac27761463732ba9cb883b93f56aa53 | [log] [tgz] |
---|---|---|
author | Vikram Auradkar <auradkar@google.com> | Thu Jun 16 00:19:18 2022 +0000 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 16 21:13:55 2022 +0000 |
tree | bc906e3ccdbb836dba9e18b400ca8963dc6067a1 | |
parent | a059bff15223dd019dd4395f5301c43a5386ad7c [diff] |
tracing: Add noop tracing BUG=b:213154559 TEST=presubmit Change-Id: Idfe23544c8381e664d913c4a80742f4e25a30006 Change-Id: I2bb0b59098ae183c45e92fcf15e1bcfe834df204 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3707622 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Vikram Auradkar <auradkar@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.