commit | 34d958f58141dc2474a9b64686b31c54a2741a8c | [log] [tgz] |
---|---|---|
author | Zhao Liu <zhao1.liu@intel.corp-partner.google.com> | Wed May 11 11:10:03 2022 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 12 04:54:11 2022 |
tree | c541454cf992f2d39d2537080a979bbd73796f55 | |
parent | f6173ca7bb2020072da8e3f4d7a41406081dc1cd [diff] |
crosvm: Add MSR handler after setting CPU affinity For MSR handlers with "from running CPU" configuration, they will open and store the MSR file descriptior immediately while their creation. So move their creation after crosvm sets CPU affinity for each vCPU thread can avoid storing redundant MSR file fds. BUG=b:225375705 TEST=Set `--userspace-msr=0x1a2,type=r,action=pass,from=cpu0` Change-Id: Iaa7bf804595ef45eec150e826be87c86ffeeef24 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3641478 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Junichi Uekawa <uekawa@chromium.org> Commit-Queue: Junichi Uekawa <uekawa@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 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.