commit | f79c1092e504c50464cf5ac1328fc21f198c418a | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Fri Feb 09 11:24:18 2024 -0800 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 10 22:36:41 2024 +0000 |
tree | 0ce571a890da83e525ea22076688269bb012acbf | |
parent | d37c7df5be63ba71423fcc3a7796cd0bf014f5cc [diff] |
hypervisor: aarch64: set/get vector APIs Allow getting and setting vector registers through a separate API, since they are 128 bits wide, unlike other registers exposed via get_one_reg() and set_one_reg(). BUG=b:323354478 TEST=tools/dev_container tools/presubmit Change-Id: I6cf51472fed893f33a0ecebf124597a0227f6580 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5440819 Reviewed-by: Frederick Mayle <fmayle@google.com> Commit-Queue: Daniel Verkamp <dverkamp@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.