commit | 4257db14895bdb52f6bc7aa721d4ea4ceb656317 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Wed Mar 15 13:18:22 2023 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 15 21:43:14 2023 +0000 |
tree | 548b358c2bc872d4f7666ce168fe76166aba38bd | |
parent | b96ba4c8bee41be937907b0fc05caf978cdde948 [diff] |
hypervisor: remove nmi.pad field from VcpuEvents This seems to be purely reserved for alignment reasons; the kernel never touches it, so we don't need to serialize/deserialize it. BUG=b:266515147 TEST=tools/presubmit Change-Id: I3074d24f50a8e0e86340c398885c2fbef1410a88 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4342173 Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Elie Kheirallah <khei@google.com> Reviewed-by: Frederick Mayle <fmayle@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 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.