commit | 49d7f75f82b60a963243ba490b0a1a89a7e1a22b | [log] [tgz] |
---|---|---|
author | Natsuko Mineno <natsukomineno@chromium.org> | Fri Sep 15 01:09:10 2023 +0000 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 29 07:16:59 2023 +0000 |
tree | 50bcb5b912b4df3bfaac03435ea1236be6195393 | |
parent | c7dddbcc44833f89b3b2e98630baea5e84be1b9c [diff] |
cros_tracing_analyser: Add histogram Extract name and latency of cros_tracing events output it to json file BUG=b:297954291 TEST= Run the tool with a trace.dat collected by trace-cmd. Change-Id: I2871bdbfc1ba2819fe27ba017e12be93e2d3cee0 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4866140 Commit-Queue: Natsuko Mineno <natsukomineno@google.com> Reviewed-by: Morg <morg@google.com> Reviewed-by: Takaya Saeki <takayas@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 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.