commit | 29e018652f8a78be9d874d77d060be7de9afc7a4 | [log] [tgz] |
---|---|---|
author | Noah Gold <nkgold@google.com> | Thu Mar 09 20:35:59 2023 -0800 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 14 18:24:44 2023 +0000 |
tree | 47ba9fb2d567b182d85d116e7b702869795b3a9f | |
parent | 341a4a6f4fbd430f2041a61eceeab0de8dc863fb [diff] |
base: move read/write wrappers to their own module. In the future we'll be using read/write wrappers in multiple places, but the wrapping code currently lives in the named pipe implementation. This CL pulls it out to its own module. It also brings in some other code in win_util that wasn't upstreamed. BUG=b:272614458 TEST=presubmit Change-Id: I6871f3db6991336f42706652b69935755bf2fbc3 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4326942 Commit-Queue: Noah Gold <nkgold@google.com> Reviewed-by: 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.