| commit | 048757ea4fbbb43d25f483acd1b94b27047b21bd | [log] [tgz] |
|---|---|---|
| author | Yiwei Zhang <zzyiwei@chromium.org> | Sat Dec 02 23:42:40 2023 -0800 |
| committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Dec 07 21:18:39 2023 +0000 |
| tree | 5e5e9603d010373ddd1df1acf72067fcf2b8a15f | |
| parent | 6e3391fc92a4fbde8a5d01435d195b9b6a2b1afd [diff] |
base: linux: mmap: resolve map flags in one place There's no behavior change introduced in this commit. The map flags are able to be resolved in one place. This is to prepare for later map flags changes. BUG=b:290125852 TEST=build Change-Id: I1eb52e767967b80a327b542910648c5cac01b369 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5081863 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Yiwei Zhang <zzyiwei@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.