commit | ee53dd075dd0944a2ac6251c21dbc2c8c21b7100 | [log] [tgz] |
---|---|---|
author | Dennis Kempin <denniskempin@google.com> | Mon Feb 28 10:30:38 2022 -0800 |
committer | Dennis Kempin <denniskempin@google.com> | Mon Feb 28 21:30:13 2022 +0000 |
tree | e33dd4f8f991e9a4f02fe0a2b0c9bad3d66afd28 | |
parent | 6e81be02c3773aa706076b9c8ff2f30a89c9f4c7 [diff] |
tools/chromeos/create_merge: Automatically resolve conflicts The merge can trigger conflicts if a change has been cherry picked ahead of the merge. We always want to resolve conflicts by picking the incoming version from cros/main. BUG=None TEST=./tools/chromeos/create_merge Change-Id: I06694dd24b051fcdc12dbaccdbab552c72d7f2c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3494968 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@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 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.