mirrors/crosvm
1
0
Fork 0
mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2025-02-09 03:57:24 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
crosvm/Cargo.lock

2539 lines
49 KiB
Text
Raw Normal View History

Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
version = 3
[[package]]
name = "aarch64"
version = "0.1.0"
dependencies = [
"arch",
"base",
arch: split fdt code into its own crate This will let the hypervisor crate use types and functions from the new cros_fdt crate (it could not depend on arch, since that would cause a circular dependency). No functional change, just code movement. BUG=b:253416076 TEST=cargo build TEST=cargo build --target=aarch64-unknown-linux-gnu Change-Id: I62d906941867c45f1b77ff1db6923d915ce2123e Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3965088 Reviewed-by: Steven Moreland <smoreland@google.com> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2022-10-18 19:50:50 +00:00
"cros_fdt",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"data_model",
"devices",
gdb: Add basic support for AArch64 Enable the "gdb" feature on AArch64 (KVM) builds and add support for: - reading & writing guest memory (only guest IPAs, for now) - getting & setting core registers - getting & setting the few system registers from kvm_regs - setting hardware breakpoints (no software breakpoints, for now) - enabling single-step mode BUG=b:222222882 BUG=b:240711627 BUG=chromium:1141812 TEST=tools/dev_container ./tools/run_tests Change-Id: I0ae38c1065002d55a569b1575b1637110694e6db Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3785467 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Takaya Saeki <takayas@chromium.org>
2022-08-31 11:51:38 +00:00
"gdbstub",
"gdbstub_arch",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"hypervisor",
"kernel_cmdline",
"kernel_loader",
"kvm",
"kvm_sys",
"libc",
"memoffset 0.6.5",
"minijail",
"remain",
"resources",
"sync",
"thiserror",
"vm_control",
"vm_memory",
]
[[package]]
name = "acpi_tables"
version = "0.1.0"
dependencies = [
"data_model",
"tempfile",
]
[[package]]
name = "aho-corasick"
version = "0.7.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1e37cfd5e7657ada45f742d6e99ca5788580b5c529dc78faf11ece6dc702656f"
dependencies = [
"memchr",
]
[[package]]
name = "ansi_term"
version = "0.12.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d52a9bb7ec0cf484c551830a7ce27bd20d67eac647e1befb56b0be4ee39a55d2"
dependencies = [
"winapi",
]
[[package]]
name = "anti_tamper"
version = "0.1.0"
dependencies = [
"base",
]
[[package]]
name = "anyhow"
version = "1.0.58"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bb07d2053ccdbe10e2af2995a2f116c1330396493dc1269f6a91d0ae82e19704"
crosvm-fuzz: Migrate crosvm-fuzz to cargo fuzz Fuzzer targets can be ran with cargo +nightly fuzz run --fuzz-dir crosvm-fuzz --features upstream-fuzz <target> This should enable us to move fuzzing to anywhere including ClusterFuzz while maintain compatibility with cros infra. TEST=`cargo fuzz` won't crash in first 30s, `USE="asan fuzzer" emerge-hatch crosvm` builds, `/build/hatch/usr/libexec/fuzzers/crosvm_qcow_fuzzer` won't crash in first 30s FIXED=b:245007212 BUG=b:244631591 Change-Id: I4b262ee1a6a90247dea96347c55a3849af793bec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3905095 Auto-Submit: Zihan Chen <zihanchen@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-21 01:34:10 +00:00
[[package]]
name = "arbitrary"
Revert "Remove crosvm-fuzz from workspace" This reverts commit e2171ea4b7bcf4799b34b69aa9002ba5873c8fee. Reason for revert: Breaks crosvm-fuzz builds Original change's description: > Remove crosvm-fuzz from workspace > > The fuzz binary targets do not compile upstream. > This allows us to run all unit tests via cargo. > > BUG=None > TEST=cargo test --workspace --lib --bins > > Change-Id: I3923c79a8d622824956599b9b8552c7d1a610b70 > Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4015006 > Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Bug: None Change-Id: Iedc1a8e8335e82cf543650ae811c1e0a83668b76 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4021756 Auto-Submit: Dennis Kempin <denniskempin@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-11-11 00:40:22 +00:00
version = "1.1.6"
crosvm-fuzz: Migrate crosvm-fuzz to cargo fuzz Fuzzer targets can be ran with cargo +nightly fuzz run --fuzz-dir crosvm-fuzz --features upstream-fuzz <target> This should enable us to move fuzzing to anywhere including ClusterFuzz while maintain compatibility with cros infra. TEST=`cargo fuzz` won't crash in first 30s, `USE="asan fuzzer" emerge-hatch crosvm` builds, `/build/hatch/usr/libexec/fuzzers/crosvm_qcow_fuzzer` won't crash in first 30s FIXED=b:245007212 BUG=b:244631591 Change-Id: I4b262ee1a6a90247dea96347c55a3849af793bec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3905095 Auto-Submit: Zihan Chen <zihanchen@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-21 01:34:10 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert "Remove crosvm-fuzz from workspace" This reverts commit e2171ea4b7bcf4799b34b69aa9002ba5873c8fee. Reason for revert: Breaks crosvm-fuzz builds Original change's description: > Remove crosvm-fuzz from workspace > > The fuzz binary targets do not compile upstream. > This allows us to run all unit tests via cargo. > > BUG=None > TEST=cargo test --workspace --lib --bins > > Change-Id: I3923c79a8d622824956599b9b8552c7d1a610b70 > Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4015006 > Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Bug: None Change-Id: Iedc1a8e8335e82cf543650ae811c1e0a83668b76 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4021756 Auto-Submit: Dennis Kempin <denniskempin@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-11-11 00:40:22 +00:00
checksum = "f44124848854b941eafdb34f05b3bcf59472f643c7e151eba7c2b69daa469ed5"
crosvm-fuzz: Migrate crosvm-fuzz to cargo fuzz Fuzzer targets can be ran with cargo +nightly fuzz run --fuzz-dir crosvm-fuzz --features upstream-fuzz <target> This should enable us to move fuzzing to anywhere including ClusterFuzz while maintain compatibility with cros infra. TEST=`cargo fuzz` won't crash in first 30s, `USE="asan fuzzer" emerge-hatch crosvm` builds, `/build/hatch/usr/libexec/fuzzers/crosvm_qcow_fuzzer` won't crash in first 30s FIXED=b:245007212 BUG=b:244631591 Change-Id: I4b262ee1a6a90247dea96347c55a3849af793bec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3905095 Auto-Submit: Zihan Chen <zihanchen@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-21 01:34:10 +00:00
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "arch"
version = "0.1.0"
dependencies = [
"acpi_tables",
"anyhow",
"base",
"cfg-if",
arch: split fdt code into its own crate This will let the hypervisor crate use types and functions from the new cros_fdt crate (it could not depend on arch, since that would cause a circular dependency). No functional change, just code movement. BUG=b:253416076 TEST=cargo build TEST=cargo build --target=aarch64-unknown-linux-gnu Change-Id: I62d906941867c45f1b77ff1db6923d915ce2123e Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3965088 Reviewed-by: Steven Moreland <smoreland@google.com> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2022-10-18 19:50:50 +00:00
"cros_fdt",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"devices",
gdb: Make feature less x86_64-centric Remove target_arch-specific #[cfg]s where the underlying code is architecture-agnostic. Introduce a GdbOps trait for architectures to implement. Make use of the generic gdbstub::arch::Arch trait where relevant. Import base::Tube unconditionally in arch/src/sys/unix.rs. Expand crate::gdb::* in vm_control/src/lib.rs for clarity. Keep target_arch checks in x86-specific code to exclude 32-bit builds as those don't seem to provide GDB support. BUG=b:222222882 BUG=chromium:1141812 TEST=tools/dev_container ./tools/run_tests Change-Id: I3f5ceeeb9031bee222ecd388dddb815e256748e8 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3785464 Tested-by: Pierre-Clément Tosi <ptosi@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Auto-Submit: Pierre-Clément Tosi <ptosi@google.com> Commit-Queue: Pierre-Clément Tosi <ptosi@google.com>
2022-07-04 10:58:14 +00:00
"gdbstub",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"gdbstub_arch",
"hypervisor",
"kernel_cmdline",
"libc",
"minijail",
"power_monitor",
"remain",
"resources",
"serde",
crosvm: use serde_keyvalue to build Pstore We had a manual parsing function that is strictly equivalent to how serde_keyvalue would deserialize, so do the latter instead. Also add some tests to make sure we don't regress in the future. BUG=b:218223240 TEST=./tools/health-check Change-Id: I5b6317774368fa4256a1944e7aec54e8fe8f210a Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3979494 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2022-10-25 06:52:41 +00:00
"serde_keyvalue",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"sync",
"thiserror",
"vm_control",
"vm_memory",
"winapi",
]
[[package]]
name = "argh"
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a7e7e4aa7e40747e023c0761dafcb42333a9517575bbf1241747f68dd3177a62"
dependencies = [
"argh_derive",
"argh_shared",
]
[[package]]
name = "argh_derive"
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "69f2bd7ff6ed6414f4e5521bd509bae46454bbd513801767ced3f21a751ab4bc"
dependencies = [
"argh_shared",
"heck",
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "argh_helpers"
version = "0.1.0"
dependencies = [
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "argh_shared"
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "47253b98986dafc7a3e1cf3259194f1f47ac61abb57a57f46ec09e48d004ecda"
[[package]]
name = "async-task"
version = "4.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a40729d2133846d9ed0ea60a8b9541bccddab49cd30f0715a1da672fe9a2524"
[[package]]
name = "async-trait"
version = "0.1.56"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "96cf8829f67d2eab0b2dfa42c5d0ef737e0724e4a82b01b3e292456202b19716"
dependencies = [
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "atty"
version = "0.2.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
dependencies = [
"hermit-abi",
"libc",
"winapi",
]
[[package]]
name = "audio_streams"
version = "0.1.0"
dependencies = [
"async-trait",
"futures",
"remain",
audio_streams_conformance_test: add playback test for NoopStream The first version of audio_streams_conformance_test. It is used to test if the implementation of audio_streams::AsyncPlaybackBufferStream is correct. This version only supports the playback test of NoopStream. It prints the following information for NoopStream. == Playback Source: NoopStream Channels: 2 Format: S16LE Sample rate: 48000 frames/s Buffer size: 240 frames Iterations: 10 Cold start latency: 3.89µs Records count: 10 [Step] min: 4.94 ms, max: 5.15 ms, average: 5.01 ms, standard deviation: 0.06 ms. [Linear Regression] rate: 47916.19 frames/s, standard error: 2.0 BUG=b:238038707 TEST=cargo run Change-Id: Ifca7dfd35473ffd75856a27e2c6aa1555eba7576 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3805090 Tested-by: Judy Hsiao <judyhsiao@google.com> Reviewed-by: Chih-Yang Hsia <paulhsia@chromium.org> Commit-Queue: Chih-Yang Hsia <paulhsia@chromium.org> Auto-Submit: Judy Hsiao <judyhsiao@google.com>
2022-07-28 14:55:16 +00:00
"serde",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"thiserror",
]
[[package]]
name = "autocfg"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa"
[[package]]
name = "balloon_control"
version = "0.1.0"
dependencies = [
"serde",
]
[[package]]
name = "base"
version = "0.1.0"
dependencies = [
"audio_streams",
"base_event_token_derive",
"cfg-if",
"chrono",
"data_model",
"env_logger",
"libc",
"log",
Reland "base: unix: add fork_process" This is a reland of commit 77688e305d53d9b4eb52bba17147755ae1234cce Tests are ignored on some architectures due to the single thread test issues b/258371694 Original change's description: > base: unix: add fork_process > > The vmm-swap feature will fork a process to run monitoring userfaultfd. > > crosvm uses minijail to fork device processes `ProxyDevice::new()`. > > Minijail panics on fork if there are any other threads running. The test > must be executed in a single thread. > > design document: go/tanooki-phase1-dd > > BUG=b:215093219 > TEST=cargo test -p base -- --test-threads=1 > > Change-Id: I408dbfa4d606cbe7b2218096b414512710d60100 > Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3935683 > Reviewed-by: David Stevens <stevensd@chromium.org> Bug: b:215093219 Change-Id: I94b912b04947cada3e3332861f18988873dfcf81 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4015626 Reviewed-by: David Stevens <stevensd@chromium.org> Commit-Queue: David Stevens <stevensd@chromium.org> Auto-Submit: Shin Kawamura <kawasin@google.com>
2022-10-05 01:39:07 +00:00
"minijail",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"once_cell",
crosvm: fold windows-only proto-tube-hack into kiwi Makes proto-tube the default behavior when kiwi is enabled. BUG=b:244666222 TEST=tested downstream Change-Id: I4281dec4dc201ff981662498dae932b514c34050 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3881729 Commit-Queue: Vikram Auradkar <auradkar@google.com> Reviewed-by: Richard Zhang <rizhang@google.com> Auto-Submit: Vikram Auradkar <auradkar@google.com> Tested-by: Vikram Auradkar <auradkar@google.com>
2022-09-08 02:45:46 +00:00
"protobuf",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"rand",
"regex",
"remain",
"serde",
"serde_json",
"smallvec",
"sync",
"tempfile",
"thiserror",
"uuid",
"win_util",
"winapi",
]
[[package]]
name = "base_event_token_derive"
version = "0.1.0"
dependencies = [
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
[[package]]
name = "bindgen"
version = "0.60.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "062dddbc1ba4aca46de6338e2bf87771414c335f7b2f2036e8f3e9befebf88e6"
dependencies = [
"bitflags",
"cexpr",
"clang-sys",
"lazy_static",
"lazycell",
"peeking_take_while",
"proc-macro2",
"quote 1.0.21",
"regex",
"rustc-hash",
"shlex",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "bit_field"
version = "0.1.0"
dependencies = [
"bit_field_derive",
]
[[package]]
name = "bit_field_derive"
version = "0.1.0"
dependencies = [
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "bitflags"
version = "1.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
media: cros-codecs: Introduce the cros-codecs crate Introduce the cros-codecs crate. This crate contains all the codec-related code and does not depend on CrosVM. The decoders are decoupled from the backends, which allows for the implementation of new backends without touching the decoder code. This crate comes with dummy backends to test the decoder functionality in isolation, but in order to decode frames, a real backend is needed. Currently this backend is the VAAPI backend. Using it adds a dependency on the libva crate. This change adds support for VP8, H264 and VP9. BUG=b:214478588 TEST="cd media/cros-codecs && cargo test --release --features vaapi -- --include-ignored" TEST="emerge-hatch chromeos-base/crosvm" completes successfully. Change-Id: I596d5db4dabcc96dcfdbce1f41c8092e01b64271 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3875043 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2022-09-03 23:35:41 +00:00
[[package]]
name = "bitreader"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d84ea71c85d1fe98fe67a9b9988b1695bc24c0b0d3bfb18d4c510f44b4b09941"
dependencies = [
"cfg-if",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "broker_ipc"
version = "0.1.0"
dependencies = [
"anyhow",
"base",
crash-report: Build with feature crash-report BUG: b:244618109 TEST: Presubmit and built with the feature on windows and linux. Change-Id: Idf9ae87243eb0a7c7b9a6ff525406f1430b49c20 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3916339 Commit-Queue: Vikram Auradkar <auradkar@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-23 19:06:38 +00:00
"crash_report",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"metrics",
"serde",
]
[[package]]
name = "byteorder"
version = "1.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "14c189c53d098945499cdfa7ecc63567cf3886b3332b312a5b4585d8d3a6a610"
[[package]]
name = "bytes"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f0b3de4a0c5e67e16066a0715723abd91edc2f9001d09c46e1dca929351e130e"
[[package]]
name = "cbindgen"
version = "0.20.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "51e3973b165dc0f435831a9e426de67e894de532754ff7a3f307c03ee5dec7dc"
dependencies = [
"clap",
"heck",
"indexmap",
"log",
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"serde",
"serde_json",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"tempfile",
"toml",
]
[[package]]
name = "cc"
version = "1.0.73"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2fff2a6927b3bb87f9595d67196a70493f627687a71d87a0d692242c33f58c11"
crosvm-fuzz: Migrate crosvm-fuzz to cargo fuzz Fuzzer targets can be ran with cargo +nightly fuzz run --fuzz-dir crosvm-fuzz --features upstream-fuzz <target> This should enable us to move fuzzing to anywhere including ClusterFuzz while maintain compatibility with cros infra. TEST=`cargo fuzz` won't crash in first 30s, `USE="asan fuzzer" emerge-hatch crosvm` builds, `/build/hatch/usr/libexec/fuzzers/crosvm_qcow_fuzzer` won't crash in first 30s FIXED=b:245007212 BUG=b:244631591 Change-Id: I4b262ee1a6a90247dea96347c55a3849af793bec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3905095 Auto-Submit: Zihan Chen <zihanchen@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-21 01:34:10 +00:00
dependencies = [
"jobserver",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
[[package]]
name = "cexpr"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6fac387a98bb7c37292057cffc56d62ecb629900026402633ae9160df93a8766"
dependencies = [
"nom",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
[[package]]
name = "chrono"
version = "0.4.19"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "670ad68c9088c2a963aaa298cb369688cf3f9465ce5e2d4ca10e6e0098a1ce73"
dependencies = [
"libc",
"num-integer",
"num-traits",
"serde",
"time",
"winapi",
]
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
[[package]]
name = "clang-sys"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fa2e27ae6ab525c3d369ded447057bca5438d86dc3a68f6faafb8269ba82ebf3"
dependencies = [
"glob",
"libc",
"libloading",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "clap"
version = "2.34.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a0610544180c38b88101fecf2dd634b174a62eef6946f84dfc6a7127512b381c"
dependencies = [
"ansi_term",
"atty",
"bitflags",
"strsim",
"textwrap",
"unicode-width",
"vec_map",
]
[[package]]
name = "const-sha1"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fb58b6451e8c2a812ad979ed1d83378caa5e927eef2622017a45f251457c2c9d"
crash-report: Build with feature crash-report BUG: b:244618109 TEST: Presubmit and built with the feature on windows and linux. Change-Id: Idf9ae87243eb0a7c7b9a6ff525406f1430b49c20 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3916339 Commit-Queue: Vikram Auradkar <auradkar@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-23 19:06:38 +00:00
[[package]]
name = "crash_report"
version = "0.1.0"
dependencies = [
"anyhow",
"base",
"serde",
"win_util",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "crc32fast"
version = "1.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b540bd8bc810d3885c6ea91e2018302f68baba2129ab3e88f32389ee9370880d"
dependencies = [
"cfg-if",
]
media: cros-codecs: Introduce the cros-codecs crate Introduce the cros-codecs crate. This crate contains all the codec-related code and does not depend on CrosVM. The decoders are decoupled from the backends, which allows for the implementation of new backends without touching the decoder code. This crate comes with dummy backends to test the decoder functionality in isolation, but in order to decode frames, a real backend is needed. Currently this backend is the VAAPI backend. Using it adds a dependency on the libva crate. This change adds support for VP8, H264 and VP9. BUG=b:214478588 TEST="cd media/cros-codecs && cargo test --release --features vaapi -- --include-ignored" TEST="emerge-hatch chromeos-base/crosvm" completes successfully. Change-Id: I596d5db4dabcc96dcfdbce1f41c8092e01b64271 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3875043 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2022-09-03 23:35:41 +00:00
[[package]]
name = "cros-codecs"
version = "0.1.0"
dependencies = [
"anyhow",
"bitreader",
"bytes",
"crc32fast",
"downcast-rs",
"enumn",
"libva",
"log",
"thiserror",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "cros_async"
version = "0.1.1"
dependencies = [
"anyhow",
"async-task",
"async-trait",
"audio_streams",
"base",
"cfg-if",
"data_model",
"futures",
"futures-executor",
"futures-util",
"intrusive-collections",
"io_uring",
"libc",
"once_cell",
"paste",
"pin-utils",
"remain",
"serde",
cros_async: refactor FromStr for ExecutorKind FromStr trait is manually implemented for ExecutorKind, but serd_keyvalue should be preferred. This commits refactors ExecutorKind so that derives serd_keyvalue. BUG=None TEST=`crosvm --async-executor (epoll|uring) run ...` works TEST=test passes on linux and windows Change-Id: I5aafb6704c20a17120b30c290e1a4069dff9e5ce Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3924880 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Takaya Saeki <takayas@chromium.org>
2022-09-29 09:25:23 +00:00
"serde_keyvalue",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"slab",
"smallvec",
"sync",
"tempfile",
"thiserror",
"win_util",
"winapi",
]
Make common crates part of the crosvm workspace This greatly simplifies and speeds up compilation and clippy times. This ChromeOS-side building these crates has been updated to copy the source out of the source tree so that they will compile as a separate workspace. BUG=b:256020427 TEST=presubmit Change-Id: I2e0f1f6724924d6bdd70ea28d7777df7966cf724 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988324 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-10-27 17:24:36 +00:00
[[package]]
name = "cros_asyncv2"
version = "0.2.0"
dependencies = [
"anyhow",
"async-task",
"base",
"data_model",
"futures",
"futures-executor",
"futures-util",
"intrusive-collections",
"io-uring",
"libc",
"memoffset 0.6.5",
"mio",
"once_cell",
"slab",
"smallvec",
"sync",
"tempfile",
"thiserror",
]
arch: split fdt code into its own crate This will let the hypervisor crate use types and functions from the new cros_fdt crate (it could not depend on arch, since that would cause a circular dependency). No functional change, just code movement. BUG=b:253416076 TEST=cargo build TEST=cargo build --target=aarch64-unknown-linux-gnu Change-Id: I62d906941867c45f1b77ff1db6923d915ce2123e Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3965088 Reviewed-by: Steven Moreland <smoreland@google.com> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2022-10-18 19:50:50 +00:00
[[package]]
name = "cros_fdt"
version = "0.1.0"
dependencies = [
"anyhow",
"remain",
"thiserror",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "cros_fuzz"
version = "0.1.0"
dependencies = [
crosvm-fuzz: Migrate crosvm-fuzz to cargo fuzz Fuzzer targets can be ran with cargo +nightly fuzz run --fuzz-dir crosvm-fuzz --features upstream-fuzz <target> This should enable us to move fuzzing to anywhere including ClusterFuzz while maintain compatibility with cros infra. TEST=`cargo fuzz` won't crash in first 30s, `USE="asan fuzzer" emerge-hatch crosvm` builds, `/build/hatch/usr/libexec/fuzzers/crosvm_qcow_fuzzer` won't crash in first 30s FIXED=b:245007212 BUG=b:244631591 Change-Id: I4b262ee1a6a90247dea96347c55a3849af793bec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3905095 Auto-Submit: Zihan Chen <zihanchen@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-21 01:34:10 +00:00
"libfuzzer-sys",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"rand_core",
]
tracing: rename tracing to cros_tracing. `tracing` conflicts with a crates.io crate. Since we may support tokio tracing in the future, and want to submit some benchmarks against it right now, we should rename our crate. BUG=b:253517247 TEST=presubmit Change-Id: I32bf64a7ce1830e881bd582e4606932782df65c6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3957598 Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Vikram Auradkar <auradkar@google.com> Commit-Queue: Noah Gold <nkgold@google.com>
2022-10-14 22:14:39 +00:00
[[package]]
name = "cros_tracing"
version = "0.1.0"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "crossbeam-utils"
version = "0.8.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "51887d4adc7b564537b15adcfb307936f8075dfcd5f00dde9a9f1d29383682bc"
dependencies = [
"cfg-if",
"once_cell",
]
[[package]]
name = "crosvm"
version = "0.1.0"
dependencies = [
"aarch64",
"acpi_tables",
"anti_tamper",
"anyhow",
"arch",
"argh",
"argh_helpers",
"audio_streams",
"base",
"bit_field",
"broker_ipc",
crosvm: Embed seccomp filters into binary Seccomp policy files will now pre-compile to bpf bytecode for target architecture and embedded in the crosvm binary when not built for chrome os. When minijail is not checked out in crosvm tree as a submodule, MINIJAIL_DIR environment variable needs to be specified for the policy compiler to run. Integration tests are now sandbox enabled for better coverage. TEST=all tests passed, vm runs fine with sandbox on and no separate policy files present. cros deploy & crostini still works. BUG=b:235858187 FIXED=b:226975168 Change-Id: Ieaba4b3d7160ccb342a297ebc374894d19a8dc4d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3824062 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: Zihan Chen <zihanchen@google.com> Commit-Queue: Zihan Chen <zihanchen@google.com>
2022-07-20 00:26:21 +00:00
"cc",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"cfg-if",
crash-report: Build with feature crash-report BUG: b:244618109 TEST: Presubmit and built with the feature on windows and linux. Change-Id: Idf9ae87243eb0a7c7b9a6ff525406f1430b49c20 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3916339 Commit-Queue: Vikram Auradkar <auradkar@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-23 19:06:38 +00:00
"crash_report",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"cros_async",
tracing: rename tracing to cros_tracing. `tracing` conflicts with a crates.io crate. Since we may support tokio tracing in the future, and want to submit some benchmarks against it right now, we should rename our crate. BUG=b:253517247 TEST=presubmit Change-Id: I32bf64a7ce1830e881bd582e4606932782df65c6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3957598 Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Vikram Auradkar <auradkar@google.com> Commit-Queue: Noah Gold <nkgold@google.com>
2022-10-14 22:14:39 +00:00
"cros_tracing",
src: move exit module to new crosvm_cli crate. Since we have "main" like functions in the devices crate for vhost-user devices, we need to use ExitContext & Exit there. This wasn't possible with the existing location in the crosvm/main crate because crosvm -> devices so we can't have devices -> crosvm. This CL moves exit to a new crate, crosvm_cli, where it can be used by all interested consumers. BUG=b:253348635 TEST=builds Change-Id: Ia06d9dee2cd5826ea20a7fb3a0c2a53c58e2ff1d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3960854 Commit-Queue: Noah Gold <nkgold@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-10-17 20:42:19 +00:00
"crosvm_cli",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"crosvm_plugin",
"ctrlc",
"data_model",
"devices",
"disk",
Document feature flags and introduce new feature sets The feature flags are documented using the document_features crate. Each platform gets one feature set that enables the features that are built and tested for that platform. The only functional difference is that the plugin feature is now enabled in clippy. Otherwise this should be a no-op. BUG=b:243894033 TEST=presubmit && cargo doc Change-Id: Ia910bc2670696172daedcc503f7ad5844a844964 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3946024 Reviewed-by: Vikram Auradkar <auradkar@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-10-11 19:53:23 +00:00
"document-features",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"enumn",
"futures",
"gdbstub",
"gdbstub_arch",
"gpu_display",
"hypervisor",
"kernel_cmdline",
"kernel_loader",
"kvm",
"kvm_sys",
"libc",
"libcras",
"log",
crosvm: add JSON configuration file support Add a new `--cfg` command-line parameter, which allows a single (for now) JSON configuration file to be specified and loaded as the base configuration for the VM, if the `config-file` feature is enabled (the default). Configuration options in the file can be overriden or extended by the regular command-line arguments. Typically, options that can be specified only once are overriden, and options that can be specified several times (like `--block`) are extended, allowing some devices of the same type to be declared in a configuration file and some more on the command-line. Due to a limitation in argh, which does not yet allow `Option<bool>` fields to be used as switches, merging more than a single configuration file is not reliable so we only support a single configuration file for now. This has been addressed upstream but not yet in a released version. Configuration file support for all the options of RunCommand increases the crosvm binary size compiled with the `chromeos` profile by 250KB. However, due to the currently limited set of options in the configuration file, the present CL increases the binary size by just 78KB. Without the `config-file` feature, this CL does not incur any binary size increase. Supported parameters as of this commit: * battery * block * executable-path * initrd * net * params * serial * socket BUG=b:218223240 TEST=`cargo run --features config-file -- run --cfg vm.json` boots the VM with parameters defined in vm.json. Change-Id: Ibb27556144ee766af81c178e5b94bd5117e102da Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3970368 Reviewed-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-10-20 06:40:27 +00:00
"merge",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"metrics",
"minijail",
"net_util",
"once_cell",
"p9",
prebuilts: move prebuilts tests under tests BUG=b:246987526 TEST=presubmit Change-Id: I86eed7c84f7e21eb7155695489ee9446f999dc1d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3936733 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-10-06 20:17:00 +00:00
"prebuilts",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"protobuf",
"protos",
"rand",
"remain",
"resources",
"rutabaga_gfx",
sandbox: upstream sandbox The crate depends on a prebuilt library. BUG=b:213170185 TEST=presubmit Change-Id: I810baa14afa53e88f6b2a739481a6d3656efc2e5 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3784338 Commit-Queue: Vikram Auradkar <auradkar@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-07-27 05:19:25 +00:00
"sandbox",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"scudo",
"serde",
"serde_json",
"serde_keyvalue",
Replace common/assertions with static_assertions The crates do the same thing, but static_assertions is proven and stable, with no added dependencies. Note: While this won't require changes to chromeos ebuild files it will require the removal of dev-rust/assertions when crosvm-base is upreved. BUG=b:255989923 TEST=presbumit Change-Id: I1420447ebdaa1a3649b30e6a6ec57f8dee858b98 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988328 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-10-27 19:30:07 +00:00
"static_assertions",
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
"swap",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"sync",
"tempfile",
"terminal_size",
"thiserror",
"tube_transporter",
"uuid",
"vhost",
"vm_control",
"vm_memory",
build.rs: find compile_seccomp_policy via which If a copy of the compile_seccomp_policy program that is used to generate BPF versions of the seccomp policies is available in the $PATH, use it in preference to the one in the submodule. This makes the ChromeOS ebuild able to embed seccomp policies, since it has compile_secomp_policy installed as part of the cros_sdk, so the special case for CROSVM_BUILD_VARIANT is removed. BUG=b:235858187 TEST=emerge-kevin crosvm # with submodules deinitialized Change-Id: I30f23a507ee444bc3fe5d78af394fbe651191be0 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3998113 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2022-11-02 01:16:50 +00:00
"which",
win_audio: build and test win_audio BUG=b:253494168 TEST=presubmit Change-Id: Icb729671a0dcfbc4b6251c69732784de32f6318d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988069 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Auto-Submit: Vikram Auradkar <auradkar@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-10-17 21:24:42 +00:00
"win_audio",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"win_util",
"winapi",
"x86_64",
]
Revert "Remove crosvm-fuzz from workspace" This reverts commit e2171ea4b7bcf4799b34b69aa9002ba5873c8fee. Reason for revert: Breaks crosvm-fuzz builds Original change's description: > Remove crosvm-fuzz from workspace > > The fuzz binary targets do not compile upstream. > This allows us to run all unit tests via cargo. > > BUG=None > TEST=cargo test --workspace --lib --bins > > Change-Id: I3923c79a8d622824956599b9b8552c7d1a610b70 > Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4015006 > Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Bug: None Change-Id: Iedc1a8e8335e82cf543650ae811c1e0a83668b76 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4021756 Auto-Submit: Dennis Kempin <denniskempin@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-11-11 00:40:22 +00:00
[[package]]
name = "crosvm-fuzz"
version = "0.0.1"
dependencies = [
"base",
"cros_fuzz",
"data_model",
"devices",
"disk",
"fuse",
"hypervisor",
"kernel_loader",
"libc",
"rand",
"tempfile",
"usb_util",
"vm_memory",
]
src: move exit module to new crosvm_cli crate. Since we have "main" like functions in the devices crate for vhost-user devices, we need to use ExitContext & Exit there. This wasn't possible with the existing location in the crosvm/main crate because crosvm -> devices so we can't have devices -> crosvm. This CL moves exit to a new crate, crosvm_cli, where it can be used by all interested consumers. BUG=b:253348635 TEST=builds Change-Id: Ia06d9dee2cd5826ea20a7fb3a0c2a53c58e2ff1d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3960854 Commit-Queue: Noah Gold <nkgold@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-10-17 20:42:19 +00:00
[[package]]
name = "crosvm_cli"
version = "0.1.0"
dependencies = [
"anyhow",
"cfg-if",
"win_util",
"winapi",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "crosvm_control"
version = "0.1.0"
dependencies = [
"anyhow",
"base",
"cbindgen",
"libc",
"vm_control",
]
[[package]]
name = "crosvm_plugin"
version = "0.17.0"
dependencies = [
"base",
"kvm",
"kvm_sys",
"libc",
"protobuf",
"protos",
]
[[package]]
name = "ctrlc"
version = "3.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b37feaa84e6861e00a1f5e5aa8da3ee56d605c9992d33e082786754828e20865"
dependencies = [
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
"nix 0.24.2",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"winapi",
]
[[package]]
name = "data_model"
version = "0.1.0"
dependencies = [
"cfg-if",
"libc",
"remain",
"serde",
Replace common/assertions with static_assertions The crates do the same thing, but static_assertions is proven and stable, with no added dependencies. Note: While this won't require changes to chromeos ebuild files it will require the removal of dev-rust/assertions when crosvm-base is upreved. BUG=b:255989923 TEST=presbumit Change-Id: I1420447ebdaa1a3649b30e6a6ec57f8dee858b98 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988328 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-10-27 19:30:07 +00:00
"static_assertions",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"thiserror",
"winapi",
]
[[package]]
name = "dbus"
version = "0.9.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6f8bcdd56d2e5c4ed26a529c5a9029f5db8290d433497506f958eae3be148eb6"
dependencies = [
"libc",
"libdbus-sys",
"winapi",
]
[[package]]
name = "derive-into-owned"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "576fce04d31d592013a5887ba8d9c3830adff329e5096d7e1eb5e8e61262ca62"
dependencies = [
"quote 0.3.15",
"syn 0.11.11",
]
[[package]]
name = "devices"
version = "0.1.0"
dependencies = [
"acpi_tables",
"anyhow",
"argh",
"async-task",
"audio_streams",
"balloon_control",
"base",
"bit_field",
"broker_ipc",
"bytes",
"cfg-if",
"chrono",
"crc32fast",
video: decoder: vaapi: port the VAAPI backend to cros-codecs Port the VAAPI backend to the new cros-codecs crate. This crate now contains all codec related code and is independent from the rest of the CrosVM code. BUG=b:214478588 TEST="cargo test --package devices --lib --features video-decoder --features vaapi -- virtio::video::decoder::backend::vaapi::tests::test_get_capabilities --include-ignored" Change-Id: Id207c53c0c4200e03ce8793d7c37cb5fbe808829 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3875044 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2022-09-05 12:21:09 +00:00
"cros-codecs",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"cros_async",
tracing: rename tracing to cros_tracing. `tracing` conflicts with a crates.io crate. Since we may support tokio tracing in the future, and want to submit some benchmarks against it right now, we should rename our crate. BUG=b:253517247 TEST=presubmit Change-Id: I32bf64a7ce1830e881bd582e4606932782df65c6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3957598 Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Vikram Auradkar <auradkar@google.com> Commit-Queue: Noah Gold <nkgold@google.com>
2022-10-14 22:14:39 +00:00
"cros_tracing",
devices: add err code for disk image open failed. Adds a new error code for when we fail to open a disk image. Also adds an exit code we were missing upstream. BUG=b:253348635 TEST=intentionally messed up the disk image path and verified we get this error. Change-Id: I197b4c5d80682dd1ee2a42d02df852276d204c17 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3961530 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Noah Gold <nkgold@google.com>
2022-10-17 20:47:21 +00:00
"crosvm_cli",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"data_model",
"dbus",
"disk",
"downcast-rs",
"enumn",
"ffmpeg",
"fuse",
"futures",
"gpu_display",
"hypervisor",
"kvm_sys",
"libc",
"libcras",
"libva",
"libvda",
"linux_input_sys",
"memoffset 0.6.5",
"metrics",
"minijail",
"net_sys",
"net_util",
"num-traits",
"once_cell",
"p9",
"power_monitor",
"protobuf",
"protos",
"rand",
"regex",
"remain",
"resources",
"rutabaga_gfx",
"serde",
"serde_json",
"serde_keyvalue",
"smallvec",
"sync",
"system_api",
"tempfile",
"thiserror",
"tpm2",
"tube_transporter",
"usb_util",
"uuid",
"vfio_sys",
"vhost",
"virtio_sys",
"vm_control",
"vm_memory",
"vmm_vhost",
win_audio: build and test win_audio BUG=b:253494168 TEST=presubmit Change-Id: Icb729671a0dcfbc4b6251c69732784de32f6318d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988069 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Auto-Submit: Vikram Auradkar <auradkar@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-10-17 21:24:42 +00:00
"win_audio",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"win_util",
"winapi",
]
[[package]]
name = "disk"
version = "0.1.0"
dependencies = [
"async-trait",
"base",
"cfg-if",
"crc32fast",
"cros_async",
"data_model",
"futures",
"libc",
"protobuf",
"protos",
"remain",
"serde",
disk: add AsyncDiskFileWrapper As a stepping stone toward fully asynchronous disk formats, add a wrapper that takes a regular synchronous DiskFile and provides the async disk API. BUG=b:219595052 TEST=cargo build --features=composite-disk Change-Id: Id785ad7ff69ae869a8a9007134fdb4fe7f3be4ba Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3824066 Tested-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com>
2022-05-13 20:27:00 +00:00
"sync",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"tempfile",
"thiserror",
"uuid",
"vm_memory",
]
Document feature flags and introduce new feature sets The feature flags are documented using the document_features crate. Each platform gets one feature set that enables the features that are built and tested for that platform. The only functional difference is that the plugin feature is now enabled in clippy. Otherwise this should be a no-op. BUG=b:243894033 TEST=presubmit && cargo doc Change-Id: Ia910bc2670696172daedcc503f7ad5844a844964 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3946024 Reviewed-by: Vikram Auradkar <auradkar@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-10-11 19:53:23 +00:00
[[package]]
name = "document-features"
version = "0.2.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c3267e1ade4f1f6ddd35fed44a04b6514e244ffeda90c6a14a9ee30f9c9fd7a1"
dependencies = [
"litrs",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "downcast-rs"
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9ea835d29036a4087793836fa931b08837ad5e957da9e23886b29586fb9b6650"
Rename integration_tests to e2e_tests Cargo already uses the term 'integration test' for tests living in the tests/ directory of a crate. To prevent confusion, rename our 'integration_tests' crate to 'e2e_tests'. BUG=None TEST=presubmit Change-Id: Icfa819eaed08be54ab0f36092f1ba367f3f1ce88 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4004977 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zihan Chen <zihanchen@google.com>
2022-11-03 21:28:42 +00:00
[[package]]
name = "e2e_tests"
version = "0.1.0"
dependencies = [
"anyhow",
"arch",
"base",
"cfg-if",
"libc",
"prebuilts",
e2e_tests: vsock: use a random cid for a guest Using a fixed CID may cause conflict with another guest easily. Change to use a random CID for a test VM. BUG=b:258072662 TEST=`./tools/presubmit` Change-Id: I1f3bab8bd64664b1b2feb480a6d0e285ea4099bb Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4012278 Commit-Queue: Ryuichiro Chiba <chibar@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-11-08 02:22:07 +00:00
"rand",
Rename integration_tests to e2e_tests Cargo already uses the term 'integration test' for tests living in the tests/ directory of a crate. To prevent confusion, rename our 'integration_tests' crate to 'e2e_tests'. BUG=None TEST=presubmit Change-Id: Icfa819eaed08be54ab0f36092f1ba367f3f1ce88 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4004977 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Zihan Chen <zihanchen@google.com>
2022-11-03 21:28:42 +00:00
"tempfile",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "either"
version = "1.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f107b87b6afc2a64fd13cac55fe06d6c8859f12d4b14cbcdd2c67d0976781be"
[[package]]
name = "enumn"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "052bc8773a98bd051ff37db74a8a25f00e6bfa2cbd03373390c72e9f7afbf344"
dependencies = [
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "env_logger"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0b2cf0344971ee6c64c31be0d530793fba457d322dfec2810c453d0ef228f9c3"
dependencies = [
"atty",
"humantime",
"log",
"regex",
"termcolor",
]
gpu_display: upstream Windows implementation On Windows, we have to create a GUI thread that creates the window and retrieves window messages from the thread-specific message queue created by the system. All host events, such as window resizing and mouse and keyboard events, are sent in the form of window messages. Hence, we created these structs/traits to model it: - `Window`: Owns the handle of one window, and provides helper functions for operating on this window. - `HandleWindowMessage`: A trait implemented by the struct that processes host events. In our case, that is the surface. - `WindowMessageProcessor`: Holds one `Window` object and one `HandleWindowMessage` trait object. We only support one window for now. Once we support multi-windowing, there will be multiple processors. - `WindowMessageDispatcher`: A singleton, responsible for dispatching messages retrieved from the message queue to the targeted processor. - `WindowProcedureThread`: Wraps the GUI thread, retrieves messages from the message queue and forwards them to the dispatcher. It also provides helper functions for other threads to talk to the GUI thread. - `MessageRelayThread`: Relays service messages to the GUI thread. Main difference from other platforms: event devices are imported to the GUI thread, since all host events are processed there. BUG=b:213150276 TEST=presubmit Change-Id: I0aabf6adf8a9ff4b24375e9c7df7625b6f761c7a Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3834009 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org> Commit-Queue: Pujun Lun <lunpujun@google.com>
2022-08-16 21:12:11 +00:00
[[package]]
name = "euclid"
version = "0.22.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b52c2ef4a78da0ba68fbe1fd920627411096d2ac478f7f4c9f3a54ba6705bade"
dependencies = [
"num-traits",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "fastrand"
version = "1.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a7a407cfaa3385c4ae6b23e84623d48c2798d06e3e6a1878f7f59f17b3f86499"
dependencies = [
"instant",
]
[[package]]
name = "ffmpeg"
version = "0.1.0"
dependencies = [
"anyhow",
"libc",
"pkg-config",
"thiserror",
]
[[package]]
name = "fnv"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
[[package]]
name = "fuse"
version = "0.1.0"
dependencies = [
"base",
"bitflags",
"crossbeam-utils",
"data_model",
"enumn",
"libc",
"remain",
"thiserror",
]
[[package]]
name = "futures"
version = "0.3.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f73fe65f54d1e12b726f517d3e2135ca3125a437b6d998caf1962961f7172d9e"
dependencies = [
"futures-channel",
"futures-core",
"futures-executor",
"futures-io",
"futures-sink",
"futures-task",
"futures-util",
]
[[package]]
name = "futures-channel"
version = "0.3.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c3083ce4b914124575708913bca19bfe887522d6e2e6d0952943f5eac4a74010"
dependencies = [
"futures-core",
"futures-sink",
]
[[package]]
name = "futures-core"
version = "0.3.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0c09fd04b7e4073ac7156a9539b57a484a8ea920f79c7c675d05d289ab6110d3"
[[package]]
name = "futures-executor"
version = "0.3.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9420b90cfa29e327d0429f19be13e7ddb68fa1cccb09d65e5706b8c7a749b8a6"
dependencies = [
"futures-core",
"futures-task",
"futures-util",
"num_cpus",
]
[[package]]
name = "futures-io"
version = "0.3.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fc4045962a5a5e935ee2fdedaa4e08284547402885ab326734432bed5d12966b"
[[package]]
name = "futures-macro"
version = "0.3.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "33c1e13800337f4d4d7a316bf45a567dbcb6ffe087f16424852d97e97a91f512"
dependencies = [
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "futures-sink"
version = "0.3.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "21163e139fa306126e6eedaf49ecdb4588f939600f0b1e770f4205ee4b7fa868"
[[package]]
name = "futures-task"
version = "0.3.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "57c66a976bf5909d801bbef33416c41372779507e7a6b3a5e25e4749c58f776a"
[[package]]
name = "futures-util"
version = "0.3.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d8b7abd5d659d9b90c8cba917f6ec750a74e2dc23902ef9cd4cc8c8b22e6036a"
dependencies = [
"futures-channel",
"futures-core",
"futures-io",
"futures-macro",
"futures-sink",
"futures-task",
"memchr",
"pin-project-lite",
"pin-utils",
"slab",
]
[[package]]
name = "gdbstub"
gdb: Upgrade gdbstub & gdbstub_arch dependencies Bump the versions of these crates as we're about to require support for unavailable register values and AArch64. Do it in a separate commit to ease future bisects. BUG=b:222222882 BUG=chromium:1141812 TEST=tools/dev_container ./tools/run_tests Change-Id: I0bfa3559d172faf2df6bcffdc77714830f442051 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3785466 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Auto-Submit: Pierre-Clément Tosi <ptosi@google.com> Tested-by: Pierre-Clément Tosi <ptosi@google.com> Commit-Queue: Pierre-Clément Tosi <ptosi@google.com> Reviewed-by: Takaya Saeki <takayas@chromium.org>
2022-07-25 12:28:01 +00:00
version = "0.6.3"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
gdb: Upgrade gdbstub & gdbstub_arch dependencies Bump the versions of these crates as we're about to require support for unavailable register values and AArch64. Do it in a separate commit to ease future bisects. BUG=b:222222882 BUG=chromium:1141812 TEST=tools/dev_container ./tools/run_tests Change-Id: I0bfa3559d172faf2df6bcffdc77714830f442051 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3785466 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Auto-Submit: Pierre-Clément Tosi <ptosi@google.com> Tested-by: Pierre-Clément Tosi <ptosi@google.com> Commit-Queue: Pierre-Clément Tosi <ptosi@google.com> Reviewed-by: Takaya Saeki <takayas@chromium.org>
2022-07-25 12:28:01 +00:00
checksum = "32c95766e0414f8bfc1d07055574c621b67739466d6ba516c4fef8e99d30d2e6"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
dependencies = [
"bitflags",
"cfg-if",
"log",
"managed",
"num-traits",
"paste",
]
[[package]]
name = "gdbstub_arch"
gdb: Upgrade gdbstub & gdbstub_arch dependencies Bump the versions of these crates as we're about to require support for unavailable register values and AArch64. Do it in a separate commit to ease future bisects. BUG=b:222222882 BUG=chromium:1141812 TEST=tools/dev_container ./tools/run_tests Change-Id: I0bfa3559d172faf2df6bcffdc77714830f442051 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3785466 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Auto-Submit: Pierre-Clément Tosi <ptosi@google.com> Tested-by: Pierre-Clément Tosi <ptosi@google.com> Commit-Queue: Pierre-Clément Tosi <ptosi@google.com> Reviewed-by: Takaya Saeki <takayas@chromium.org>
2022-07-25 12:28:01 +00:00
version = "0.2.4"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
gdb: Upgrade gdbstub & gdbstub_arch dependencies Bump the versions of these crates as we're about to require support for unavailable register values and AArch64. Do it in a separate commit to ease future bisects. BUG=b:222222882 BUG=chromium:1141812 TEST=tools/dev_container ./tools/run_tests Change-Id: I0bfa3559d172faf2df6bcffdc77714830f442051 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3785466 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Auto-Submit: Pierre-Clément Tosi <ptosi@google.com> Tested-by: Pierre-Clément Tosi <ptosi@google.com> Commit-Queue: Pierre-Clément Tosi <ptosi@google.com> Reviewed-by: Takaya Saeki <takayas@chromium.org>
2022-07-25 12:28:01 +00:00
checksum = "eecb536c55c43593a00dde9074dbbdb0e81ce5f20dbca921400f8779c21dea9c"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
dependencies = [
"gdbstub",
"num-traits",
]
[[package]]
name = "getrandom"
version = "0.2.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4eb1a864a501629691edf6c15a593b7a51eebaa1e8468e9ddc623de7c9b58ec6"
dependencies = [
"cfg-if",
"libc",
"wasi 0.11.0+wasi-snapshot-preview1",
]
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
[[package]]
name = "glob"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9b919933a397b79c37e33b77bb2aa3dc8eb6e165ad809e58ff75bc7db2e34574"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "gpu_display"
version = "0.1.0"
dependencies = [
gpu_display: upstream Windows implementation On Windows, we have to create a GUI thread that creates the window and retrieves window messages from the thread-specific message queue created by the system. All host events, such as window resizing and mouse and keyboard events, are sent in the form of window messages. Hence, we created these structs/traits to model it: - `Window`: Owns the handle of one window, and provides helper functions for operating on this window. - `HandleWindowMessage`: A trait implemented by the struct that processes host events. In our case, that is the surface. - `WindowMessageProcessor`: Holds one `Window` object and one `HandleWindowMessage` trait object. We only support one window for now. Once we support multi-windowing, there will be multiple processors. - `WindowMessageDispatcher`: A singleton, responsible for dispatching messages retrieved from the message queue to the targeted processor. - `WindowProcedureThread`: Wraps the GUI thread, retrieves messages from the message queue and forwards them to the dispatcher. It also provides helper functions for other threads to talk to the GUI thread. - `MessageRelayThread`: Relays service messages to the GUI thread. Main difference from other platforms: event devices are imported to the GUI thread, since all host events are processed there. BUG=b:213150276 TEST=presubmit Change-Id: I0aabf6adf8a9ff4b24375e9c7df7625b6f761c7a Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3834009 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org> Commit-Queue: Pujun Lun <lunpujun@google.com>
2022-08-16 21:12:11 +00:00
"anyhow",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"base",
"cc",
"cfg-if",
"data_model",
gpu_display: upstream Windows implementation On Windows, we have to create a GUI thread that creates the window and retrieves window messages from the thread-specific message queue created by the system. All host events, such as window resizing and mouse and keyboard events, are sent in the form of window messages. Hence, we created these structs/traits to model it: - `Window`: Owns the handle of one window, and provides helper functions for operating on this window. - `HandleWindowMessage`: A trait implemented by the struct that processes host events. In our case, that is the surface. - `WindowMessageProcessor`: Holds one `Window` object and one `HandleWindowMessage` trait object. We only support one window for now. Once we support multi-windowing, there will be multiple processors. - `WindowMessageDispatcher`: A singleton, responsible for dispatching messages retrieved from the message queue to the targeted processor. - `WindowProcedureThread`: Wraps the GUI thread, retrieves messages from the message queue and forwards them to the dispatcher. It also provides helper functions for other threads to talk to the GUI thread. - `MessageRelayThread`: Relays service messages to the GUI thread. Main difference from other platforms: event devices are imported to the GUI thread, since all host events are processed there. BUG=b:213150276 TEST=presubmit Change-Id: I0aabf6adf8a9ff4b24375e9c7df7625b6f761c7a Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3834009 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org> Commit-Queue: Pujun Lun <lunpujun@google.com>
2022-08-16 21:12:11 +00:00
"euclid",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"libc",
"linux_input_sys",
gpu_display: upstream Windows implementation On Windows, we have to create a GUI thread that creates the window and retrieves window messages from the thread-specific message queue created by the system. All host events, such as window resizing and mouse and keyboard events, are sent in the form of window messages. Hence, we created these structs/traits to model it: - `Window`: Owns the handle of one window, and provides helper functions for operating on this window. - `HandleWindowMessage`: A trait implemented by the struct that processes host events. In our case, that is the surface. - `WindowMessageProcessor`: Holds one `Window` object and one `HandleWindowMessage` trait object. We only support one window for now. Once we support multi-windowing, there will be multiple processors. - `WindowMessageDispatcher`: A singleton, responsible for dispatching messages retrieved from the message queue to the targeted processor. - `WindowProcedureThread`: Wraps the GUI thread, retrieves messages from the message queue and forwards them to the dispatcher. It also provides helper functions for other threads to talk to the GUI thread. - `MessageRelayThread`: Relays service messages to the GUI thread. Main difference from other platforms: event devices are imported to the GUI thread, since all host events are processed there. BUG=b:213150276 TEST=presubmit Change-Id: I0aabf6adf8a9ff4b24375e9c7df7625b6f761c7a Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3834009 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org> Commit-Queue: Pujun Lun <lunpujun@google.com>
2022-08-16 21:12:11 +00:00
"metrics",
"num-traits",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"pkg-config",
"remain",
gpu_display: upstream Windows implementation On Windows, we have to create a GUI thread that creates the window and retrieves window messages from the thread-specific message queue created by the system. All host events, such as window resizing and mouse and keyboard events, are sent in the form of window messages. Hence, we created these structs/traits to model it: - `Window`: Owns the handle of one window, and provides helper functions for operating on this window. - `HandleWindowMessage`: A trait implemented by the struct that processes host events. In our case, that is the surface. - `WindowMessageProcessor`: Holds one `Window` object and one `HandleWindowMessage` trait object. We only support one window for now. Once we support multi-windowing, there will be multiple processors. - `WindowMessageDispatcher`: A singleton, responsible for dispatching messages retrieved from the message queue to the targeted processor. - `WindowProcedureThread`: Wraps the GUI thread, retrieves messages from the message queue and forwards them to the dispatcher. It also provides helper functions for other threads to talk to the GUI thread. - `MessageRelayThread`: Relays service messages to the GUI thread. Main difference from other platforms: event devices are imported to the GUI thread, since all host events are processed there. BUG=b:213150276 TEST=presubmit Change-Id: I0aabf6adf8a9ff4b24375e9c7df7625b6f761c7a Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3834009 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org> Commit-Queue: Pujun Lun <lunpujun@google.com>
2022-08-16 21:12:11 +00:00
"serde",
"sync",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"thiserror",
gpu_display: upstream Windows implementation On Windows, we have to create a GUI thread that creates the window and retrieves window messages from the thread-specific message queue created by the system. All host events, such as window resizing and mouse and keyboard events, are sent in the form of window messages. Hence, we created these structs/traits to model it: - `Window`: Owns the handle of one window, and provides helper functions for operating on this window. - `HandleWindowMessage`: A trait implemented by the struct that processes host events. In our case, that is the surface. - `WindowMessageProcessor`: Holds one `Window` object and one `HandleWindowMessage` trait object. We only support one window for now. Once we support multi-windowing, there will be multiple processors. - `WindowMessageDispatcher`: A singleton, responsible for dispatching messages retrieved from the message queue to the targeted processor. - `WindowProcedureThread`: Wraps the GUI thread, retrieves messages from the message queue and forwards them to the dispatcher. It also provides helper functions for other threads to talk to the GUI thread. - `MessageRelayThread`: Relays service messages to the GUI thread. Main difference from other platforms: event devices are imported to the GUI thread, since all host events are processed there. BUG=b:213150276 TEST=presubmit Change-Id: I0aabf6adf8a9ff4b24375e9c7df7625b6f761c7a Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3834009 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org> Commit-Queue: Pujun Lun <lunpujun@google.com>
2022-08-16 21:12:11 +00:00
"vm_control",
"win_util",
"winapi",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "hashbrown"
version = "0.12.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8a9ee70c43aaf417c914396645a0fa852624801b24ebb7ae78fe8272889ac888"
[[package]]
name = "heck"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6d621efb26863f0e9924c6ac577e8275e5e6b77455db64ffa6c65c904e9e132c"
dependencies = [
"unicode-segmentation",
]
[[package]]
name = "hermit-abi"
version = "0.1.19"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "62b467343b94ba476dcb2500d242dadbb39557df889310ac77c5d99100aaac33"
dependencies = [
"libc",
]
[[package]]
name = "humantime"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9a3a5bfb195931eeb336b2a7b4d761daec841b97f947d34394601737a7bba5e4"
[[package]]
name = "hypervisor"
version = "0.1.0"
dependencies = [
"base",
"bit_field",
"bitflags",
"data_model",
"downcast-rs",
"enumn",
"fnv",
gdb: Add basic support for AArch64 Enable the "gdb" feature on AArch64 (KVM) builds and add support for: - reading & writing guest memory (only guest IPAs, for now) - getting & setting core registers - getting & setting the few system registers from kvm_regs - setting hardware breakpoints (no software breakpoints, for now) - enabling single-step mode BUG=b:222222882 BUG=b:240711627 BUG=chromium:1141812 TEST=tools/dev_container ./tools/run_tests Change-Id: I0ae38c1065002d55a569b1575b1637110694e6db Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3785467 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Takaya Saeki <takayas@chromium.org>
2022-08-31 11:51:38 +00:00
"gdbstub",
"gdbstub_arch",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"kvm",
"kvm_sys",
"libc",
"memoffset 0.6.5",
"once_cell",
"serde",
"sync",
"tempfile",
"thiserror",
"vm_memory",
"win_util",
"winapi",
]
[[package]]
name = "indexmap"
version = "1.9.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "10a35a97730320ffe8e2d410b5d3b69279b98d2c14bdb8b70ea89ecf7888d41e"
dependencies = [
"autocfg",
"hashbrown",
]
[[package]]
name = "instant"
version = "0.1.12"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a5bbe824c507c5da5956355e86a746d82e0e1464f65d862cc5e71da70e94b2c"
dependencies = [
"cfg-if",
]
[[package]]
name = "intrusive-collections"
version = "0.9.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bfe531a7789d7120f3e17d4f3f2cd95f54418ba7354f60b7b622b6644a07888a"
dependencies = [
"memoffset 0.5.6",
]
Make common crates part of the crosvm workspace This greatly simplifies and speeds up compilation and clippy times. This ChromeOS-side building these crates has been updated to copy the source out of the source tree so that they will compile as a separate workspace. BUG=b:256020427 TEST=presubmit Change-Id: I2e0f1f6724924d6bdd70ea28d7777df7966cf724 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988324 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-10-27 17:24:36 +00:00
[[package]]
name = "io-uring"
version = "0.5.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "00d78c9f2db2a9800dfd15c69543896dae2135112dde0d1944442e83da8ce23a"
dependencies = [
"bitflags",
"libc",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "io_uring"
version = "0.1.1"
dependencies = [
"base",
"data_model",
"libc",
"remain",
"sync",
"tempfile",
"thiserror",
]
[[package]]
name = "itoa"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "112c678d4050afce233f4f2852bb2eb519230b3cf12f33585275537d7e41578d"
crosvm-fuzz: Migrate crosvm-fuzz to cargo fuzz Fuzzer targets can be ran with cargo +nightly fuzz run --fuzz-dir crosvm-fuzz --features upstream-fuzz <target> This should enable us to move fuzzing to anywhere including ClusterFuzz while maintain compatibility with cros infra. TEST=`cargo fuzz` won't crash in first 30s, `USE="asan fuzzer" emerge-hatch crosvm` builds, `/build/hatch/usr/libexec/fuzzers/crosvm_qcow_fuzzer` won't crash in first 30s FIXED=b:245007212 BUG=b:244631591 Change-Id: I4b262ee1a6a90247dea96347c55a3849af793bec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3905095 Auto-Submit: Zihan Chen <zihanchen@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-21 01:34:10 +00:00
[[package]]
name = "jobserver"
Revert "Remove crosvm-fuzz from workspace" This reverts commit e2171ea4b7bcf4799b34b69aa9002ba5873c8fee. Reason for revert: Breaks crosvm-fuzz builds Original change's description: > Remove crosvm-fuzz from workspace > > The fuzz binary targets do not compile upstream. > This allows us to run all unit tests via cargo. > > BUG=None > TEST=cargo test --workspace --lib --bins > > Change-Id: I3923c79a8d622824956599b9b8552c7d1a610b70 > Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4015006 > Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Bug: None Change-Id: Iedc1a8e8335e82cf543650ae811c1e0a83668b76 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4021756 Auto-Submit: Dennis Kempin <denniskempin@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-11-11 00:40:22 +00:00
version = "0.1.24"
crosvm-fuzz: Migrate crosvm-fuzz to cargo fuzz Fuzzer targets can be ran with cargo +nightly fuzz run --fuzz-dir crosvm-fuzz --features upstream-fuzz <target> This should enable us to move fuzzing to anywhere including ClusterFuzz while maintain compatibility with cros infra. TEST=`cargo fuzz` won't crash in first 30s, `USE="asan fuzzer" emerge-hatch crosvm` builds, `/build/hatch/usr/libexec/fuzzers/crosvm_qcow_fuzzer` won't crash in first 30s FIXED=b:245007212 BUG=b:244631591 Change-Id: I4b262ee1a6a90247dea96347c55a3849af793bec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3905095 Auto-Submit: Zihan Chen <zihanchen@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-21 01:34:10 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert "Remove crosvm-fuzz from workspace" This reverts commit e2171ea4b7bcf4799b34b69aa9002ba5873c8fee. Reason for revert: Breaks crosvm-fuzz builds Original change's description: > Remove crosvm-fuzz from workspace > > The fuzz binary targets do not compile upstream. > This allows us to run all unit tests via cargo. > > BUG=None > TEST=cargo test --workspace --lib --bins > > Change-Id: I3923c79a8d622824956599b9b8552c7d1a610b70 > Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4015006 > Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Bug: None Change-Id: Iedc1a8e8335e82cf543650ae811c1e0a83668b76 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4021756 Auto-Submit: Dennis Kempin <denniskempin@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-11-11 00:40:22 +00:00
checksum = "af25a77299a7f711a01975c35a6a424eb6862092cc2d6c72c4ed6cbc56dfc1fa"
crosvm-fuzz: Migrate crosvm-fuzz to cargo fuzz Fuzzer targets can be ran with cargo +nightly fuzz run --fuzz-dir crosvm-fuzz --features upstream-fuzz <target> This should enable us to move fuzzing to anywhere including ClusterFuzz while maintain compatibility with cros infra. TEST=`cargo fuzz` won't crash in first 30s, `USE="asan fuzzer" emerge-hatch crosvm` builds, `/build/hatch/usr/libexec/fuzzers/crosvm_qcow_fuzzer` won't crash in first 30s FIXED=b:245007212 BUG=b:244631591 Change-Id: I4b262ee1a6a90247dea96347c55a3849af793bec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3905095 Auto-Submit: Zihan Chen <zihanchen@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-21 01:34:10 +00:00
dependencies = [
"libc",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "kernel_cmdline"
version = "0.1.0"
dependencies = [
"libc",
"remain",
"thiserror",
]
[[package]]
name = "kernel_loader"
version = "0.1.0"
dependencies = [
"base",
"data_model",
"libc",
"remain",
"resources",
"tempfile",
"thiserror",
"vm_memory",
]
[[package]]
name = "kvm"
version = "0.1.0"
dependencies = [
"base",
"data_model",
"kvm_sys",
"libc",
"sync",
"vm_memory",
]
[[package]]
name = "kvm_sys"
version = "0.1.0"
dependencies = [
"base",
"data_model",
"libc",
]
[[package]]
name = "lazy_static"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
[[package]]
name = "lazycell"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "830d08ce1d1d941e6b30645f1a0eb5643013d835ce3779a5fc208261dbe10f55"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "libc"
version = "0.2.126"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "349d5a591cd28b49e1d1037471617a32ddcda5731b99419008085f72d5a53836"
[[package]]
name = "libcras"
version = "0.1.0"
libcras_stub: Stub implementation Stub the required parts of libcras so that upstream builds with audio_cras feature BUG=b:244618503 TEST=cargo build --features audio_cras Change-Id: I21eb3bcb9a61990740b1419f124401878619481e Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3911099 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Vineeth Pillai <vineethrp@google.com>
2022-09-21 18:48:02 +00:00
dependencies = [
"audio_streams",
"serde",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "libdbus-sys"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c185b5b7ad900923ef3a8ff594083d4d9b5aea80bb4f32b8342363138c0d456b"
dependencies = [
"pkg-config",
]
crosvm-fuzz: Migrate crosvm-fuzz to cargo fuzz Fuzzer targets can be ran with cargo +nightly fuzz run --fuzz-dir crosvm-fuzz --features upstream-fuzz <target> This should enable us to move fuzzing to anywhere including ClusterFuzz while maintain compatibility with cros infra. TEST=`cargo fuzz` won't crash in first 30s, `USE="asan fuzzer" emerge-hatch crosvm` builds, `/build/hatch/usr/libexec/fuzzers/crosvm_qcow_fuzzer` won't crash in first 30s FIXED=b:245007212 BUG=b:244631591 Change-Id: I4b262ee1a6a90247dea96347c55a3849af793bec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3905095 Auto-Submit: Zihan Chen <zihanchen@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-21 01:34:10 +00:00
[[package]]
name = "libfuzzer-sys"
Revert "Remove crosvm-fuzz from workspace" This reverts commit e2171ea4b7bcf4799b34b69aa9002ba5873c8fee. Reason for revert: Breaks crosvm-fuzz builds Original change's description: > Remove crosvm-fuzz from workspace > > The fuzz binary targets do not compile upstream. > This allows us to run all unit tests via cargo. > > BUG=None > TEST=cargo test --workspace --lib --bins > > Change-Id: I3923c79a8d622824956599b9b8552c7d1a610b70 > Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4015006 > Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Bug: None Change-Id: Iedc1a8e8335e82cf543650ae811c1e0a83668b76 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4021756 Auto-Submit: Dennis Kempin <denniskempin@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-11-11 00:40:22 +00:00
version = "0.4.4"
crosvm-fuzz: Migrate crosvm-fuzz to cargo fuzz Fuzzer targets can be ran with cargo +nightly fuzz run --fuzz-dir crosvm-fuzz --features upstream-fuzz <target> This should enable us to move fuzzing to anywhere including ClusterFuzz while maintain compatibility with cros infra. TEST=`cargo fuzz` won't crash in first 30s, `USE="asan fuzzer" emerge-hatch crosvm` builds, `/build/hatch/usr/libexec/fuzzers/crosvm_qcow_fuzzer` won't crash in first 30s FIXED=b:245007212 BUG=b:244631591 Change-Id: I4b262ee1a6a90247dea96347c55a3849af793bec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3905095 Auto-Submit: Zihan Chen <zihanchen@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-21 01:34:10 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Revert "Remove crosvm-fuzz from workspace" This reverts commit e2171ea4b7bcf4799b34b69aa9002ba5873c8fee. Reason for revert: Breaks crosvm-fuzz builds Original change's description: > Remove crosvm-fuzz from workspace > > The fuzz binary targets do not compile upstream. > This allows us to run all unit tests via cargo. > > BUG=None > TEST=cargo test --workspace --lib --bins > > Change-Id: I3923c79a8d622824956599b9b8552c7d1a610b70 > Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4015006 > Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Bug: None Change-Id: Iedc1a8e8335e82cf543650ae811c1e0a83668b76 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4021756 Auto-Submit: Dennis Kempin <denniskempin@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-11-11 00:40:22 +00:00
checksum = "ae185684fe19814afd066da15a7cc41e126886c21282934225d9fc847582da58"
crosvm-fuzz: Migrate crosvm-fuzz to cargo fuzz Fuzzer targets can be ran with cargo +nightly fuzz run --fuzz-dir crosvm-fuzz --features upstream-fuzz <target> This should enable us to move fuzzing to anywhere including ClusterFuzz while maintain compatibility with cros infra. TEST=`cargo fuzz` won't crash in first 30s, `USE="asan fuzzer" emerge-hatch crosvm` builds, `/build/hatch/usr/libexec/fuzzers/crosvm_qcow_fuzzer` won't crash in first 30s FIXED=b:245007212 BUG=b:244631591 Change-Id: I4b262ee1a6a90247dea96347c55a3849af793bec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3905095 Auto-Submit: Zihan Chen <zihanchen@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-21 01:34:10 +00:00
dependencies = [
"arbitrary",
"cc",
"once_cell",
]
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
[[package]]
name = "libloading"
version = "0.7.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "efbc0f03f9a775e9f6aed295c6a1ba2253c5757a9e03d55c6caa46a681abcddd"
dependencies = [
"cfg-if",
"winapi",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "libslirp-sys"
version = "4.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2772370ce9b7fa05c7eae0bd033005e139a64d52cee498a7905b3eb5d243c5f4"
dependencies = [
"pkg-config",
]
[[package]]
name = "libudev"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ea626d3bdf40a1c5aee3bcd4f40826970cae8d80a8fec934c82a63840094dcfe"
dependencies = [
"libc",
"libudev-sys",
]
[[package]]
name = "libudev-sys"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3c8469b4a23b962c1396b9b451dda50ef5b283e8dd309d69033475fa9b334324"
dependencies = [
"libc",
"pkg-config",
]
[[package]]
name = "libva"
version = "0.1.0"
dependencies = [
"anyhow",
"base",
"bitflags",
"crc32fast",
"libudev",
"pkg-config",
]
[[package]]
name = "libvda"
version = "0.1.0"
dependencies = [
"enumn",
"libc",
"pkg-config",
]
[[package]]
name = "linux_input_sys"
version = "0.1.0"
dependencies = [
"base",
"data_model",
"libc",
]
Document feature flags and introduce new feature sets The feature flags are documented using the document_features crate. Each platform gets one feature set that enables the features that are built and tested for that platform. The only functional difference is that the plugin feature is now enabled in clippy. Otherwise this should be a no-op. BUG=b:243894033 TEST=presubmit && cargo doc Change-Id: Ia910bc2670696172daedcc503f7ad5844a844964 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3946024 Reviewed-by: Vikram Auradkar <auradkar@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-10-11 19:53:23 +00:00
[[package]]
name = "litrs"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f9275e0933cf8bb20f008924c0cb07a0692fe54d8064996520bf998de9eb79aa"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "log"
version = "0.4.17"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "abb12e687cfb44aa40f41fc3978ef76448f9b6038cad6aef4259d3c095a2382e"
dependencies = [
"cfg-if",
]
[[package]]
name = "managed"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0ca88d725a0a943b096803bd34e73a4437208b6077654cc4ecb2947a5f91618d"
[[package]]
name = "memchr"
version = "2.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2dffe52ecf27772e601905b7522cb4ef790d2cc203488bbd0e2fe85fcb74566d"
[[package]]
name = "memoffset"
version = "0.5.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "043175f069eda7b85febe4a74abbaeff828d9f8b448515d3151a14a3542811aa"
dependencies = [
"autocfg",
]
[[package]]
name = "memoffset"
version = "0.6.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5aa361d4faea93603064a027415f07bd8e1d5c88c9fbf68bf56a285428fd79ce"
dependencies = [
"autocfg",
]
crosvm: add JSON configuration file support Add a new `--cfg` command-line parameter, which allows a single (for now) JSON configuration file to be specified and loaded as the base configuration for the VM, if the `config-file` feature is enabled (the default). Configuration options in the file can be overriden or extended by the regular command-line arguments. Typically, options that can be specified only once are overriden, and options that can be specified several times (like `--block`) are extended, allowing some devices of the same type to be declared in a configuration file and some more on the command-line. Due to a limitation in argh, which does not yet allow `Option<bool>` fields to be used as switches, merging more than a single configuration file is not reliable so we only support a single configuration file for now. This has been addressed upstream but not yet in a released version. Configuration file support for all the options of RunCommand increases the crosvm binary size compiled with the `chromeos` profile by 250KB. However, due to the currently limited set of options in the configuration file, the present CL increases the binary size by just 78KB. Without the `config-file` feature, this CL does not incur any binary size increase. Supported parameters as of this commit: * battery * block * executable-path * initrd * net * params * serial * socket BUG=b:218223240 TEST=`cargo run --features config-file -- run --cfg vm.json` boots the VM with parameters defined in vm.json. Change-Id: Ibb27556144ee766af81c178e5b94bd5117e102da Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3970368 Reviewed-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-10-20 06:40:27 +00:00
[[package]]
name = "merge"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "10bbef93abb1da61525bbc45eeaff6473a41907d19f8f9aa5168d214e10693e9"
dependencies = [
"merge_derive",
"num-traits",
]
[[package]]
name = "merge_derive"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "209d075476da2e63b4b29e72a2ef627b840589588e71400a25e3565c4f849d07"
dependencies = [
"proc-macro-error",
"proc-macro2",
"quote 1.0.21",
"syn 1.0.103",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "metrics"
version = "0.1.0"
dependencies = [
"anyhow",
"base",
"cfg-if",
"chrono",
"libc",
metrics: migrate to proto_build_tools. BUG=b:256951877 TEST=builds Change-Id: Iea6ab37489e87b1c8ca3c33fbf4a0d974a9b59ca Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4021591 Reviewed-by: Vikram Auradkar <auradkar@google.com> Commit-Queue: Noah Gold <nkgold@google.com>
2022-11-10 21:23:26 +00:00
"proto_build_tools",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"protobuf",
"serde",
"serde_json",
"sync",
crosvm: move enum ProcessType to win_util. This is to keep consistency with Windows downstream code. The conversion from ProcessType to EmulatorProcessType is moved to the metrics crate as it is only used for generating metrics. BUG=b:213146388 TEST=presubmit Change-Id: Ia62f76835a1f162dd8bbc9e53fd671968c368473 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3908370 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Pujun Lun <lunpujun@google.com>
2022-09-20 21:48:39 +00:00
"win_util",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"winapi",
"wmi",
]
[[package]]
name = "minijail"
version = "0.2.3"
dependencies = [
"libc",
"minijail-sys",
]
[[package]]
name = "minijail-sys"
version = "0.0.13"
dependencies = [
"libc",
"pkg-config",
"which",
]
serde_keyvalue: use nom crate for parsing Use the nom crate for parsing. This will arguably be both simpler to read and more reliable than our current ad-hoc parser. Add a few extra tests to enforce the new rules that the new parser is supposed to enforce. BUG=b:218223240 TEST=cargo test -p serde_keyvalues -p crosvm TEST=ARCVM starts successfully. Change-Id: I4ea188ffe8aee872071c900793c50127855403ec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3822428 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2022-08-10 02:25:02 +00:00
[[package]]
name = "minimal-lexical"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "68354c5c6bd36d73ff3feceb05efa59b6acb7626617f4962be322a825e61f79a"
Make common crates part of the crosvm workspace This greatly simplifies and speeds up compilation and clippy times. This ChromeOS-side building these crates has been updated to copy the source out of the source tree so that they will compile as a separate workspace. BUG=b:256020427 TEST=presubmit Change-Id: I2e0f1f6724924d6bdd70ea28d7777df7966cf724 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988324 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-10-27 17:24:36 +00:00
[[package]]
name = "mio"
version = "0.7.14"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8067b404fe97c70829f082dec8bcf4f71225d7eaea1d8645349cb76fa06205cc"
dependencies = [
"libc",
"log",
"miow",
"ntapi",
"winapi",
]
[[package]]
name = "miow"
version = "0.3.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b9f1c5b025cda876f66ef43a113f91ebc9f4ccef34843000e0adf6ebbab84e21"
dependencies = [
"winapi",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "net_sys"
version = "0.1.0"
dependencies = [
"base",
"libc",
]
[[package]]
name = "net_util"
version = "0.1.0"
dependencies = [
net_util: Add windows slirp support BUG=b:237011316 TEST=presubmit and tested in wine Change-Id: I1b6160142b8161d4b09d3fd98dfacde354e238b4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3934818 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-10-04 20:29:10 +00:00
"anyhow",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"base",
"cfg-if",
"cros_async",
"data_model",
"libc",
"libslirp-sys",
"metrics",
"net_sys",
"pcap-file",
net_util: Add windows slirp support BUG=b:237011316 TEST=presubmit and tested in wine Change-Id: I1b6160142b8161d4b09d3fd98dfacde354e238b4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3934818 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-10-04 20:29:10 +00:00
"prebuilts",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"remain",
"serde",
Add --net option to the crosvm run command Currently, --tap-name, --tap-name, --host-ip...etc commands are all used to create a vhost-user net device. This CL unifies the command line arguments. BUG=b:246224081 TEST=run the following tests: - `cargo test -p devices virtio::net::tests` - `cargo test -p net_util` Change-Id: Ie1342f23f0951e5a81e54547bf725c0d9be19f97 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3893869 Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Koki Ryu <kokiryu@chromium.org>
2022-09-12 08:20:06 +00:00
"serde_json",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"smallvec",
"thiserror",
"virtio_sys",
"winapi",
]
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
[[package]]
name = "nix"
version = "0.23.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9f866317acbd3a240710c63f065ffb1e4fd466259045ccb504130b7f668f35c6"
dependencies = [
"bitflags",
"cc",
"cfg-if",
"libc",
"memoffset 0.6.5",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "nix"
version = "0.24.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "195cdbc1741b8134346d515b3a56a1c94b0912758009cfd53f99ea0f57b065fc"
dependencies = [
"bitflags",
"cfg-if",
"libc",
]
serde_keyvalue: use nom crate for parsing Use the nom crate for parsing. This will arguably be both simpler to read and more reliable than our current ad-hoc parser. Add a few extra tests to enforce the new rules that the new parser is supposed to enforce. BUG=b:218223240 TEST=cargo test -p serde_keyvalues -p crosvm TEST=ARCVM starts successfully. Change-Id: I4ea188ffe8aee872071c900793c50127855403ec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3822428 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2022-08-10 02:25:02 +00:00
[[package]]
name = "nom"
version = "7.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a8903e5a29a317527874d0402f867152a3d21c908bb0b933e416c65e301d4c36"
dependencies = [
"memchr",
"minimal-lexical",
]
Make common crates part of the crosvm workspace This greatly simplifies and speeds up compilation and clippy times. This ChromeOS-side building these crates has been updated to copy the source out of the source tree so that they will compile as a separate workspace. BUG=b:256020427 TEST=presubmit Change-Id: I2e0f1f6724924d6bdd70ea28d7777df7966cf724 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988324 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-10-27 17:24:36 +00:00
[[package]]
name = "ntapi"
version = "0.3.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c28774a7fd2fbb4f0babd8237ce554b73af68021b5f695a3cebd6c59bac0980f"
dependencies = [
"winapi",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "num-integer"
version = "0.1.45"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "225d3389fb3509a24c93f5c29eb6bde2586b98d9f016636dff58d7c6f7569cd9"
dependencies = [
"autocfg",
"num-traits",
]
[[package]]
name = "num-traits"
version = "0.2.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "578ede34cf02f8924ab9447f50c28075b4d3e5b269972345e7e0372b38c6cdcd"
dependencies = [
"autocfg",
]
[[package]]
name = "num_cpus"
version = "1.13.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "19e64526ebdee182341572e50e9ad03965aa510cd94427a4549448f285e957a1"
dependencies = [
"hermit-abi",
"libc",
]
[[package]]
name = "once_cell"
version = "1.13.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "18a6dbe30758c9f83eb00cbea4ac95966305f5a7772f3f42ebfc7fc7eddbd8e1"
[[package]]
name = "p9"
version = "0.1.0"
dependencies = [
"libc",
"serde",
"wire_format_derive",
]
[[package]]
name = "paste"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0c520e05135d6e763148b6426a837e239041653ba7becd2e538c076c738025fc"
[[package]]
name = "pcap-file"
version = "1.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6ad13fed1a83120159aea81b265074f21d753d157dd16b10cc3790ecba40a341"
dependencies = [
"byteorder",
"derive-into-owned",
"thiserror",
]
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
[[package]]
name = "peeking_take_while"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "19b17cddbe7ec3f8bc800887bab5e717348c95ea2ca0b1bf0837fb964dc67099"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "pin-project-lite"
version = "0.2.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e0a7ae3ac2f1173085d398531c705756c94a4c56843785df85a60c1a0afac116"
[[package]]
name = "pin-utils"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
[[package]]
name = "pkg-config"
version = "0.3.25"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1df8c4ec4b0627e53bdf214615ad287367e482558cf84b109250b37464dc03ae"
[[package]]
name = "power_monitor"
version = "0.1.0"
dependencies = [
"base",
"dbus",
"protobuf",
"protoc-rust",
"remain",
"thiserror",
]
[[package]]
name = "ppv-lite86"
version = "0.2.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "eb9f9e6e233e5c4a35559a617bf40a4ec447db2e84c20b55a6f83167b7e57872"
prebuilts: Add helper crate to download prebuilts BUG=b:246987526 TEST=presubmit Change-Id: I1e54cf4a176d48c30340d6e7925733d6a1f4ce93 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3784337 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-10-01 03:44:29 +00:00
[[package]]
name = "prebuilts"
version = "0.1.0"
dependencies = [
"anyhow",
"cfg-if",
]
crosvm: add JSON configuration file support Add a new `--cfg` command-line parameter, which allows a single (for now) JSON configuration file to be specified and loaded as the base configuration for the VM, if the `config-file` feature is enabled (the default). Configuration options in the file can be overriden or extended by the regular command-line arguments. Typically, options that can be specified only once are overriden, and options that can be specified several times (like `--block`) are extended, allowing some devices of the same type to be declared in a configuration file and some more on the command-line. Due to a limitation in argh, which does not yet allow `Option<bool>` fields to be used as switches, merging more than a single configuration file is not reliable so we only support a single configuration file for now. This has been addressed upstream but not yet in a released version. Configuration file support for all the options of RunCommand increases the crosvm binary size compiled with the `chromeos` profile by 250KB. However, due to the currently limited set of options in the configuration file, the present CL increases the binary size by just 78KB. Without the `config-file` feature, this CL does not incur any binary size increase. Supported parameters as of this commit: * battery * block * executable-path * initrd * net * params * serial * socket BUG=b:218223240 TEST=`cargo run --features config-file -- run --cfg vm.json` boots the VM with parameters defined in vm.json. Change-Id: Ibb27556144ee766af81c178e5b94bd5117e102da Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3970368 Reviewed-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-10-20 06:40:27 +00:00
[[package]]
name = "proc-macro-error"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "da25490ff9892aab3fcf7c36f08cfb902dd3e71ca0f9f9517bea02a73a5ce38c"
dependencies = [
"proc-macro-error-attr",
"proc-macro2",
"quote 1.0.21",
"syn 1.0.103",
"version_check",
]
[[package]]
name = "proc-macro-error-attr"
version = "1.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a1be40180e52ecc98ad80b184934baf3d0d29f979574e439af5a55274b35f869"
dependencies = [
"proc-macro2",
"quote 1.0.21",
"version_check",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "proc-macro2"
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
version = "1.0.47"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
checksum = "5ea3d908b0e36316caf9e9e2c4625cdde190a7e6f440d794667ed17a1855e725"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
dependencies = [
"unicode-ident",
]
proto_build_tools: add crate for proto build tools. In addition to DRYing out our proto code, we're switching to using PathBufs to reduce the potential for cross platform errors. BUG=b:256951877 TEST=builds Change-Id: Ib7588de231afe67853c099e4f81683731b9439de Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4021590 Reviewed-by: Vikram Auradkar <auradkar@google.com>
2022-11-10 21:15:53 +00:00
[[package]]
name = "proto_build_tools"
version = "0.1.0"
dependencies = [
"protoc-rust",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "protobuf"
version = "2.27.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cf7e6d18738ecd0902d30d1ad232c9125985a3422929b16c65517b38adc14f96"
dependencies = [
"serde",
"serde_derive",
]
[[package]]
name = "protobuf-codegen"
version = "2.27.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aec1632b7c8f2e620343439a7dfd1f3c47b18906c4be58982079911482b5d707"
dependencies = [
"protobuf",
]
[[package]]
name = "protoc"
version = "2.27.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c2ef1dc036942fac2470fdb8a911f125404ee9129e9e807f3d12d8589001a38f"
dependencies = [
"log",
"which",
]
[[package]]
name = "protoc-rust"
version = "2.27.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1a9e315121c8e7e21396e940a3d27f92280a6d28e3931213bf6cbfea76c5cc94"
dependencies = [
"protobuf",
"protobuf-codegen",
"protoc",
"tempfile",
]
[[package]]
name = "protos"
version = "0.1.0"
dependencies = [
"kvm_sys",
protos: migrate to new build tool & cleanup. As part of migrating to proto_build_tools, we've cleaned up some old code that was unused: * All of the ExternalProto tooling that was unused. * The vsock proto doesn't exist. BUG=b:256951877 TEST=builds Change-Id: I647395b4900d487179139050ab6750a464b528e7 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4021592 Reviewed-by: Vikram Auradkar <auradkar@google.com> Commit-Queue: Noah Gold <nkgold@google.com>
2022-11-10 21:30:26 +00:00
"proto_build_tools",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"protobuf",
]
[[package]]
name = "qcow_utils"
version = "0.1.0"
dependencies = [
"base",
"disk",
"libc",
]
[[package]]
name = "quote"
version = "0.3.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a6e920b65c65f10b2ae65c831a81a073a89edd28c7cce89475bff467ab4167a"
[[package]]
name = "quote"
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
version = "1.0.21"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
checksum = "bbe448f377a7d6961e30f5955f9b8d106c3f5e449d493ee1b125c1d43c2b5179"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
dependencies = [
"proc-macro2",
]
[[package]]
name = "rand"
version = "0.8.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "34af8d1a0e25924bc5b7c43c079c942339d8f0a8b57c39049bef581b46327404"
dependencies = [
"libc",
"rand_chacha",
"rand_core",
]
[[package]]
name = "rand_chacha"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e6c10a63a0fa32252be49d21e7709d4d4baf8d231c2dbce1eaa8141b9b127d88"
dependencies = [
"ppv-lite86",
"rand_core",
]
[[package]]
name = "rand_core"
version = "0.6.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d34f1408f55294453790c48b2f1ebbb1c5b4b7563eb1f418bcfcfdbb06ebb4e7"
dependencies = [
"getrandom",
]
[[package]]
name = "redox_syscall"
version = "0.2.15"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "534cfe58d6a18cc17120fbf4635d53d14691c1fe4d951064df9bd326178d7d5a"
dependencies = [
"bitflags",
]
[[package]]
name = "regex"
version = "1.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4c4eb3267174b8c6c2f654116623910a0fef09c4753f8dd83db29c48a0df988b"
dependencies = [
"aho-corasick",
"memchr",
"regex-syntax",
]
[[package]]
name = "regex-syntax"
version = "0.6.27"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a3f87b73ce11b1619a3c6332f45341e0047173771e8b8b73f87bfeefb7b56244"
[[package]]
name = "remain"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0c35270ea384ac1762895831cc8acb96f171468e52cec82ed9186f9416209fa4"
dependencies = [
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "remove_dir_all"
version = "0.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3acd125665422973a33ac9d3dd2df85edad0f4ae9b00dafb1a05e43a9f5ef8e7"
dependencies = [
"winapi",
]
[[package]]
name = "resources"
version = "0.1.0"
dependencies = [
"base",
"libc",
"remain",
"serde",
"thiserror",
]
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
[[package]]
name = "rustc-hash"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "rutabaga_gfx"
version = "0.1.0"
dependencies = [
"anyhow",
"base",
"cfg-if",
"data_model",
"libc",
"pkg-config",
"remain",
"serde",
"sync",
"thiserror",
]
[[package]]
name = "ryu"
version = "1.0.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f3f6f92acf49d1b98f7a81226834412ada05458b7364277387724a237f062695"
sandbox: upstream sandbox The crate depends on a prebuilt library. BUG=b:213170185 TEST=presubmit Change-Id: I810baa14afa53e88f6b2a739481a6d3656efc2e5 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3784338 Commit-Queue: Vikram Auradkar <auradkar@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-07-27 05:19:25 +00:00
[[package]]
name = "sandbox"
version = "0.1.0"
dependencies = [
"anyhow",
"base",
"prebuilts",
"win_util",
"winapi",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "scudo"
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
version = "0.1.3"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
checksum = "12bfcb1ca07a487406afea13bdb7a2f3cf88e67b39c20dfd64e1801909b5c688"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
dependencies = [
"libc",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"scudo-proc-macros",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"scudo-sys",
]
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
[[package]]
name = "scudo-proc-macros"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b3267c900aee8fbc8451235b70c5e2dae96bb19110eabc325be5d5dfed8e7461"
dependencies = [
"proc-macro2",
"quote 1.0.21",
"syn 1.0.103",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "scudo-sys"
scudo: Drop version to 0.1 This allows ChromeOS/AOSP to keep using their slightly older bugfix version number, while our Cargo.lock file is updated to the latest version that includes the build.rs fix to prevent unnecessary re-builds. BUG=None TEST=presubmit Change-Id: Ibe0a46632d9766cad7fb6bc5b6b4042da92313bf Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3984415 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-10-26 23:41:14 +00:00
version = "0.2.2"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
scudo: Drop version to 0.1 This allows ChromeOS/AOSP to keep using their slightly older bugfix version number, while our Cargo.lock file is updated to the latest version that includes the build.rs fix to prevent unnecessary re-builds. BUG=None TEST=presubmit Change-Id: Ibe0a46632d9766cad7fb6bc5b6b4042da92313bf Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3984415 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-10-26 23:41:14 +00:00
checksum = "bcdbdfb28236bf083b47d0babb07e486bb003ed85011072b023ea4ed27760ddb"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
dependencies = [
"cc",
"libc",
]
[[package]]
name = "serde"
version = "1.0.140"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fc855a42c7967b7c369eb5860f7164ef1f6f81c20c7cc1141f2a604e18723b03"
dependencies = [
"serde_derive",
]
[[package]]
name = "serde_derive"
version = "1.0.140"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6f2122636b9fe3b81f1cb25099fcf2d3f542cdb1d45940d56c713158884a05da"
dependencies = [
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "serde_json"
version = "1.0.82"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "82c2c1fdcd807d1098552c5b9a36e425e42e9fbd7c6a37a8425f390f781f7fa7"
dependencies = [
"itoa",
"ryu",
"serde",
]
[[package]]
name = "serde_keyvalue"
version = "0.1.0"
dependencies = [
"argh",
serde_keyvalue: use nom crate for parsing Use the nom crate for parsing. This will arguably be both simpler to read and more reliable than our current ad-hoc parser. Add a few extra tests to enforce the new rules that the new parser is supposed to enforce. BUG=b:218223240 TEST=cargo test -p serde_keyvalues -p crosvm TEST=ARCVM starts successfully. Change-Id: I4ea188ffe8aee872071c900793c50127855403ec Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3822428 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2022-08-10 02:25:02 +00:00
"nom",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"num-traits",
"remain",
"serde",
"serde_keyvalue_derive",
"thiserror",
]
[[package]]
name = "serde_keyvalue_derive"
version = "0.1.0"
dependencies = [
"argh",
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
[[package]]
name = "shlex"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "43b2853a4d09f215c24cc5489c992ce46052d359b5109343cbafbf26bc62f8a3"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "slab"
version = "0.4.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4614a76b2a8be0058caa9dbbaf66d988527d86d003c11a94fbd335d7661edcef"
dependencies = [
"autocfg",
]
[[package]]
name = "smallvec"
version = "1.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2fd0db749597d91ff862fd1d55ea87f7855a744a8425a64695b6fca237d1dad1"
Replace common/assertions with static_assertions The crates do the same thing, but static_assertions is proven and stable, with no added dependencies. Note: While this won't require changes to chromeos ebuild files it will require the removal of dev-rust/assertions when crosvm-base is upreved. BUG=b:255989923 TEST=presbumit Change-Id: I1420447ebdaa1a3649b30e6a6ec57f8dee858b98 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988328 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-10-27 19:30:07 +00:00
[[package]]
name = "static_assertions"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a2eb9349b6444b326872e140eb1cf5e7c522154d69e7a0ffb0fb81c06b37543f"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "strsim"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8ea5119cdb4c55b55d432abb513a0429384878c15dde60cc77b1c99de1a95a6a"
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
[[package]]
name = "swap"
version = "0.1.0"
dependencies = [
Reland "swap: suspend device processes using SIGSTOP signal" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3932497 ProcessesGuard stops all the crosvm processes except the caller process using SIGSTOP signal because we must guarantee that no one changes the guest memory contents while vmm-swap out. This is a short term solution and will be replaced with device suspension feature later. See the "Write back atomicity" section in go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I34e528bf318e5ff9277048f3daf8608e7b09ddc7 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016145 Reviewed-by: David Stevens <stevensd@chromium.org> Commit-Queue: Shin Kawamura <kawasin@google.com>
2022-10-03 07:53:15 +00:00
"anyhow",
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
"base",
Reland "swap: add swap file" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3930082 SwapFile saves the active pages in the memory region to a file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo test -p swap Change-Id: Idce637ed069665e174b36c21a32afdad2f00fea1 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016143 Reviewed-by: David Stevens <stevensd@chromium.org> Commit-Queue: Shin Kawamura <kawasin@google.com>
2022-09-30 15:36:52 +00:00
"data_model",
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
"libc",
swap: add commands for vmm-swap out Added new crosvm commands "crosvm swap enable" and "crosvm swap status". swap crate exposes SwapController to control the vmm-swap feature. When vmm-swap is enabled, all the pages on the GuestMemory are swapped out to a file and are freed to give a lot of memory back to OS. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=manually tested Change-Id: Ideb10b0119edd9f47b66c8ac61add21ac08181d4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3871758 Reviewed-by: David Stevens <stevensd@chromium.org> Commit-Queue: Shin Kawamura <kawasin@google.com>
2022-09-02 15:49:50 +00:00
"minijail",
"remain",
"serde",
swap: log page fault event The new command "crosvm swap log_pagefault <socket>" starts logging page fault events. The log file "page_fault.log" will be located under the swap directory. Pagefault event log help up debugging the vmm-swap feature and understand the memory usage of the guest os. design document: go/tanooki-phase1-dd BUG=b:253555760 TEST=manually tested. this is debug feature. Change-Id: I13e36cef873cd83179032fe8a289c8df71384644 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3954806 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: David Stevens <stevensd@chromium.org> Commit-Queue: Shin Kawamura <kawasin@google.com>
2022-10-14 08:06:52 +00:00
"serde_json",
swap: add commands for vmm-swap out Added new crosvm commands "crosvm swap enable" and "crosvm swap status". swap crate exposes SwapController to control the vmm-swap feature. When vmm-swap is enabled, all the pages on the GuestMemory are swapped out to a file and are freed to give a lot of memory back to OS. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=manually tested Change-Id: Ideb10b0119edd9f47b66c8ac61add21ac08181d4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3871758 Reviewed-by: David Stevens <stevensd@chromium.org> Commit-Queue: Shin Kawamura <kawasin@google.com>
2022-09-02 15:49:50 +00:00
"sync",
Reland "swap: add swap file" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3930082 SwapFile saves the active pages in the memory region to a file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo test -p swap Change-Id: Idce637ed069665e174b36c21a32afdad2f00fea1 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016143 Reviewed-by: David Stevens <stevensd@chromium.org> Commit-Queue: Shin Kawamura <kawasin@google.com>
2022-09-30 15:36:52 +00:00
"tempfile",
"thiserror",
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
"userfaultfd",
swap: add commands for vmm-swap out Added new crosvm commands "crosvm swap enable" and "crosvm swap status". swap crate exposes SwapController to control the vmm-swap feature. When vmm-swap is enabled, all the pages on the GuestMemory are swapped out to a file and are freed to give a lot of memory back to OS. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=manually tested Change-Id: Ideb10b0119edd9f47b66c8ac61add21ac08181d4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3871758 Reviewed-by: David Stevens <stevensd@chromium.org> Commit-Queue: Shin Kawamura <kawasin@google.com>
2022-09-02 15:49:50 +00:00
"vm_memory",
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "syn"
version = "0.11.11"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d3b891b9015c88c576343b9b3e41c2c11a51c219ef067b264bd9c8aa9b441dad"
dependencies = [
"quote 0.3.15",
"synom",
"unicode-xid",
]
[[package]]
name = "syn"
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
version = "1.0.103"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
checksum = "a864042229133ada95abf3b54fdc62ef5ccabe9515b64717bcb9a1919e59445d"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
dependencies = [
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"unicode-ident",
]
[[package]]
name = "sync"
version = "0.1.99"
[[package]]
name = "synom"
version = "0.11.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a393066ed9010ebaed60b9eafa373d4b1baac186dd7e008555b0f702b51945b6"
dependencies = [
"unicode-xid",
]
[[package]]
name = "system_api"
version = "0.1.0"
system_api: Add copy of ChromeOS's system_api Adds a script that copies the bindings we need upstream. We cannot use the original repository, as it's part of the large platform2 git repository, and the original build.rs depends on ChromeOS tooling to generate these bindings. So instead, this change adds a script that can be called from a chromiumos checkout of crosvm to update the upstream bindings. This allows us to enable certain features that talk to ChromeOS dbus services. They won't be functional upstream, but at least we can compile and test the code. To make things more consistent, we no longer replace the crate with the ChromeOS version when building for ChromeOS. BUG=b:244618505 TEST=presubmit Change-Id: I504cbf6d12b0cb50d9935f5e49b7fa72b692d45c Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3919814 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-09-26 21:20:48 +00:00
dependencies = [
"dbus",
"protobuf",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "tempfile"
version = "3.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5cdb1ef4eaeeaddc8fbd371e5017057064af0911902ef36b39801f67cc6d79e4"
dependencies = [
"cfg-if",
"fastrand",
"libc",
"redox_syscall",
"remove_dir_all",
"winapi",
]
[[package]]
name = "termcolor"
version = "1.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bab24d30b911b2376f3a13cc2cd443142f0c81dda04c118693e35b3835757755"
dependencies = [
"winapi-util",
]
[[package]]
name = "terminal_size"
version = "0.1.17"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "633c1a546cee861a1a6d0dc69ebeca693bf4296661ba7852b9d21d159e0506df"
dependencies = [
"libc",
"winapi",
]
[[package]]
name = "textwrap"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
dependencies = [
"unicode-width",
]
[[package]]
name = "thiserror"
version = "1.0.31"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bd829fe32373d27f76265620b5309d0340cb8550f523c1dda251d6298069069a"
dependencies = [
"thiserror-impl",
]
[[package]]
name = "thiserror-impl"
version = "1.0.31"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0396bc89e626244658bef819e22d0cc459e795a5ebe878e6ec336d1674a8d79a"
dependencies = [
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "time"
version = "0.1.44"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6db9e6914ab8b1ae1c260a4ae7a49b6c5611b40328a735b21862567685e73255"
dependencies = [
"libc",
"wasi 0.10.0+wasi-snapshot-preview1",
"winapi",
]
[[package]]
name = "toml"
version = "0.5.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8d82e1a7758622a465f8cee077614c73484dac5b836c02ff6a40d5d1010324d7"
dependencies = [
"serde",
]
[[package]]
name = "tpm2"
version = "0.1.0"
dependencies = [
"tpm2-sys",
]
[[package]]
name = "tpm2-sys"
version = "0.1.0"
dependencies = [
"anyhow",
"pkg-config",
]
[[package]]
name = "tube_transporter"
version = "0.1.0"
dependencies = [
"base",
"data_model",
"rand",
"serde",
"serde_json",
"thiserror",
"win_util",
"winapi",
]
[[package]]
name = "unicode-ident"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "15c61ba63f9235225a22310255a29b806b907c9b8c964bcbd0a2c70f3f2deea7"
[[package]]
name = "unicode-segmentation"
version = "1.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7e8820f5d777f6224dc4be3632222971ac30164d4a258d595640799554ebfd99"
[[package]]
name = "unicode-width"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3ed742d4ea2bd1176e236172c8429aaf54486e7ac098db29ffe6529e0ce50973"
[[package]]
name = "unicode-xid"
version = "0.0.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8c1f860d7d29cf02cb2f3f359fd35991af3d30bac52c57d265a3c461074cb4dc"
[[package]]
name = "usb_sys"
version = "0.1.0"
dependencies = [
"base",
]
[[package]]
name = "usb_util"
version = "0.1.0"
dependencies = [
"base",
"data_model",
"libc",
"remain",
Replace common/assertions with static_assertions The crates do the same thing, but static_assertions is proven and stable, with no added dependencies. Note: While this won't require changes to chromeos ebuild files it will require the removal of dev-rust/assertions when crosvm-base is upreved. BUG=b:255989923 TEST=presbumit Change-Id: I1420447ebdaa1a3649b30e6a6ec57f8dee858b98 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988328 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-10-27 19:30:07 +00:00
"static_assertions",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"thiserror",
"usb_sys",
]
Reland "swap: add userfaultfd wrapper" origin: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895235 userfaultfd enables applications to handle page faults on designated memory area. vmm-swap feature uses userfaultfd to catch page fault event and swap in the guest memory from the swap file. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=cargo build --features=swap Change-Id: I36ecfe9be988a4bc451f8edaf2ab48e25c6600f4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4016142 Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-09-14 05:18:14 +00:00
[[package]]
name = "userfaultfd"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fee2cdd3f8bdd0b98d7aa9ace35e7214a71888229d60c1cd1cd71b7c09c089d0"
dependencies = [
"bitflags",
"cfg-if",
"libc",
"nix 0.23.1",
"thiserror",
"userfaultfd-sys",
]
[[package]]
name = "userfaultfd-sys"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d2cbcf2717fa856a7226499babbbccb07353ea2fc2b27defd38bd13b1227cc78"
dependencies = [
"bindgen",
"cc",
"cfg-if",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "uuid"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bc5cf98d8186244414c848017f0e2676b3fcb46807f6668a97dfe67359a3c4b7"
dependencies = [
"getrandom",
"serde",
]
[[package]]
name = "vec_map"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f1bddf1187be692e79c5ffeab891132dfb0f236ed36a43c7ed39f1165ee20191"
crosvm: add JSON configuration file support Add a new `--cfg` command-line parameter, which allows a single (for now) JSON configuration file to be specified and loaded as the base configuration for the VM, if the `config-file` feature is enabled (the default). Configuration options in the file can be overriden or extended by the regular command-line arguments. Typically, options that can be specified only once are overriden, and options that can be specified several times (like `--block`) are extended, allowing some devices of the same type to be declared in a configuration file and some more on the command-line. Due to a limitation in argh, which does not yet allow `Option<bool>` fields to be used as switches, merging more than a single configuration file is not reliable so we only support a single configuration file for now. This has been addressed upstream but not yet in a released version. Configuration file support for all the options of RunCommand increases the crosvm binary size compiled with the `chromeos` profile by 250KB. However, due to the currently limited set of options in the configuration file, the present CL increases the binary size by just 78KB. Without the `config-file` feature, this CL does not incur any binary size increase. Supported parameters as of this commit: * battery * block * executable-path * initrd * net * params * serial * socket BUG=b:218223240 TEST=`cargo run --features config-file -- run --cfg vm.json` boots the VM with parameters defined in vm.json. Change-Id: Ibb27556144ee766af81c178e5b94bd5117e102da Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3970368 Reviewed-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-10-20 06:40:27 +00:00
[[package]]
name = "version_check"
version = "0.9.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "49874b5167b65d7193b8aba1567f5c7d93d001cafc34600cee003eda787e483f"
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "vfio_sys"
version = "0.1.0"
dependencies = [
"base",
"data_model",
]
[[package]]
name = "vhost"
version = "0.1.0"
dependencies = [
"base",
"libc",
"net_util",
"remain",
Replace common/assertions with static_assertions The crates do the same thing, but static_assertions is proven and stable, with no added dependencies. Note: While this won't require changes to chromeos ebuild files it will require the removal of dev-rust/assertions when crosvm-base is upreved. BUG=b:255989923 TEST=presbumit Change-Id: I1420447ebdaa1a3649b30e6a6ec57f8dee858b98 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988328 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-10-27 19:30:07 +00:00
"static_assertions",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"thiserror",
"virtio_sys",
"vm_memory",
]
[[package]]
name = "virtio_sys"
version = "0.1.0"
dependencies = [
"base",
"data_model",
]
[[package]]
name = "vm_control"
version = "0.1.0"
dependencies = [
"anyhow",
"balloon_control",
"base",
"cfg-if",
"data_model",
gdb: Make feature less x86_64-centric Remove target_arch-specific #[cfg]s where the underlying code is architecture-agnostic. Introduce a GdbOps trait for architectures to implement. Make use of the generic gdbstub::arch::Arch trait where relevant. Import base::Tube unconditionally in arch/src/sys/unix.rs. Expand crate::gdb::* in vm_control/src/lib.rs for clarity. Keep target_arch checks in x86-specific code to exclude 32-bit builds as those don't seem to provide GDB support. BUG=b:222222882 BUG=chromium:1141812 TEST=tools/dev_container ./tools/run_tests Change-Id: I3f5ceeeb9031bee222ecd388dddb815e256748e8 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3785464 Tested-by: Pierre-Clément Tosi <ptosi@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Auto-Submit: Pierre-Clément Tosi <ptosi@google.com> Commit-Queue: Pierre-Clément Tosi <ptosi@google.com>
2022-07-04 10:58:14 +00:00
"gdbstub",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"gdbstub_arch",
"hypervisor",
"libc",
"remain",
"resources",
"rutabaga_gfx",
"serde",
"serde_json",
devices: gpu: Support display hotplug Adds `crosvm gpu <>` commands which allows for interactively adding/listing/removing virtio-gpu displays/scanouts. Also updates the virtio gpu device to use a Map<u32, Scanout> instead of a Vec<Scanout> and always report the maximum number of displays (16) with enabled/disabled. This helps handle the case of removing a display that is not the last display number. BUG=b:163864461 TEST=cargo build TEST=cargo build (with gpu feature disabled) TEST=Android build TEST=launch Cuttlefish TEST=crosvm gpu list-displays <socket> TEST=crosvm gpu add-displays --gpu-display=width=900,height=600 --gpu-display=width=600,height=480 <socket> TEST=crosvm gpu list-displays <socket> TEST=crosvm gpu remove-displays --display-id=1 <socket> Change-Id: I7530498897eb4e84199eaeb3d66df006df62817f Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3911102 Commit-Queue: Jason Macnak <natsu@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-09-19 00:06:37 +00:00
"serde_keyvalue",
swap: add commands for vmm-swap out Added new crosvm commands "crosvm swap enable" and "crosvm swap status". swap crate exposes SwapController to control the vmm-swap feature. When vmm-swap is enabled, all the pages on the GuestMemory are swapped out to a file and are freed to give a lot of memory back to OS. design document: go/tanooki-phase1-dd BUG=b:215093219 TEST=manually tested Change-Id: Ideb10b0119edd9f47b66c8ac61add21ac08181d4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3871758 Reviewed-by: David Stevens <stevensd@chromium.org> Commit-Queue: Shin Kawamura <kawasin@google.com>
2022-09-02 15:49:50 +00:00
"swap",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"sync",
"thiserror",
"vm_memory",
crosvm: GPU and display arg parsing for Windows. This replaces the handwritten arg parser with the serde_keyvalue based parser. Eventually we will unify the arg parsing with Unix. BUG=b:233676779 TEST=cargo b --features all-msvc64,gpu --no-default-features TEST=cargo t -p vm_control --features all-msvc64,gpu --no-default-features TEST=cargo t -p crosvm sys::windows::config:: --features all-msvc64,gpu --no-default-features Change-Id: I36a563be9767c7e5cbd3ab44f6a9ba23cd64cdb6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3939033 Commit-Queue: Pujun Lun <lunpujun@google.com> Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
2022-10-07 06:35:27 +00:00
"winapi",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "vm_memory"
version = "0.1.0"
dependencies = [
"base",
"bitflags",
"cfg-if",
"cros_async",
"data_model",
"libc",
"remain",
"serde",
"thiserror",
]
[[package]]
name = "vmm_vhost"
version = "0.1.0"
dependencies = [
"anyhow",
"base",
"bitflags",
"cfg-if",
"data_model",
"libc",
"remain",
"serde",
"serde_json",
"tempfile",
"thiserror",
devices: Implement MasterReqHandler for Windows Brings up the master request handler on Windows. To stay within the existing protocol, PackedTube was introduced, which is able to transmit a Tube via a RawDescriptor. BUG=b:221882601 TEST=presubmit & cargo test & tested downstream Change-Id: Ibd4c2f55c42738392beed5b15b8d445e47890627 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3856828 Reviewed-by: David Stevens <stevensd@chromium.org> Commit-Queue: Idan Raiter <idanr@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-08-25 00:24:05 +00:00
"tube_transporter",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "wasi"
version = "0.10.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1a143597ca7c7793eff794def352d41792a93c481eb1042423ff7ff72ba2c31f"
[[package]]
name = "wasi"
version = "0.11.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9c8d87e72b64a3b4db28d11ce29237c246188f4f51057d65a7eab63b7987e423"
[[package]]
name = "which"
version = "4.2.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c4fb54e6113b6a8772ee41c3404fb0301ac79604489467e0a9ce1f3e97c24ae"
dependencies = [
"either",
"lazy_static",
"libc",
]
[[package]]
name = "widestring"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "17882f045410753661207383517a6f62ec3dbeb6a4ed2acce01f0728238d1983"
win_audio: build and test win_audio BUG=b:253494168 TEST=presubmit Change-Id: Icb729671a0dcfbc4b6251c69732784de32f6318d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988069 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Auto-Submit: Vikram Auradkar <auradkar@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-10-17 21:24:42 +00:00
[[package]]
name = "win_audio"
version = "0.1.0"
dependencies = [
"anyhow",
win_audio: Upstream Windows audio backend code The most notable changes are: * Playback Async support * Audio Client flags to hide app from SndVol when audio session has expired * Updates to audio_streams and cros_async crates for playback async support BUG=b:256655413 TEST=Verified to work downstream Change-Id: Ifbe9a15791feaa41d6e1d5eaf2c5824b2c7c25b8 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3994882 Commit-Queue: Richard Zhang <rizhang@google.com> Reviewed-by: Noah Gold <nkgold@google.com>
2022-10-31 19:37:48 +00:00
"async-trait",
win_audio: build and test win_audio BUG=b:253494168 TEST=presubmit Change-Id: Icb729671a0dcfbc4b6251c69732784de32f6318d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988069 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Auto-Submit: Vikram Auradkar <auradkar@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-10-17 21:24:42 +00:00
"audio_streams",
"base",
win_audio: Upstream Windows audio backend code The most notable changes are: * Playback Async support * Audio Client flags to hide app from SndVol when audio session has expired * Updates to audio_streams and cros_async crates for playback async support BUG=b:256655413 TEST=Verified to work downstream Change-Id: Ifbe9a15791feaa41d6e1d5eaf2c5824b2c7c25b8 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3994882 Commit-Queue: Richard Zhang <rizhang@google.com> Reviewed-by: Noah Gold <nkgold@google.com>
2022-10-31 19:37:48 +00:00
"cros_async",
win_audio: build and test win_audio BUG=b:253494168 TEST=presubmit Change-Id: Icb729671a0dcfbc4b6251c69732784de32f6318d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988069 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Auto-Submit: Vikram Auradkar <auradkar@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-10-17 21:24:42 +00:00
"libc",
"metrics",
"once_cell",
"prebuilts",
"sync",
"thiserror",
"win_util",
"winapi",
"wio",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "win_util"
version = "0.1.0"
dependencies = [
"anyhow",
crosvm: move enum ProcessType to win_util. This is to keep consistency with Windows downstream code. The conversion from ProcessType to EmulatorProcessType is moved to the metrics crate as it is only used for generating metrics. BUG=b:213146388 TEST=presubmit Change-Id: Ia62f76835a1f162dd8bbc9e53fd671968c368473 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3908370 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Pujun Lun <lunpujun@google.com>
2022-09-20 21:48:39 +00:00
"enumn",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"libc",
"once_cell",
crosvm: move enum ProcessType to win_util. This is to keep consistency with Windows downstream code. The conversion from ProcessType to EmulatorProcessType is moved to the metrics crate as it is only used for generating metrics. BUG=b:213146388 TEST=presubmit Change-Id: Ia62f76835a1f162dd8bbc9e53fd671968c368473 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3908370 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Pujun Lun <lunpujun@google.com>
2022-09-20 21:48:39 +00:00
"serde",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"winapi",
"windows",
]
[[package]]
name = "winapi"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
dependencies = [
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
]
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
[[package]]
name = "winapi-util"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
dependencies = [
"winapi",
]
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
[[package]]
name = "windows"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a43e544233e20425d5a58e9671cf76d6aed9e6f211508c050facb29b188dc10f"
dependencies = [
"const-sha1",
"windows_gen",
"windows_macros",
]
[[package]]
name = "windows_gen"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bc6283570a39b3594e31c64a498f48058758cc063eb087d972bb6476ad134a16"
[[package]]
name = "windows_macros"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f757e7665f81f33ace9f89b0f0fc3a7c770e24ff4fa1475c6503bb35b4524893"
dependencies = [
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"windows_gen",
]
win_audio: build and test win_audio BUG=b:253494168 TEST=presubmit Change-Id: Icb729671a0dcfbc4b6251c69732784de32f6318d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988069 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Auto-Submit: Vikram Auradkar <auradkar@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-10-17 21:24:42 +00:00
[[package]]
name = "wio"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5d129932f4644ac2396cb456385cbf9e63b5b30c6e8dc4820bdca4eb082037a5"
dependencies = [
"winapi",
]
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
[[package]]
name = "wire_format_derive"
version = "0.1.0"
dependencies = [
"proc-macro2",
Bump scudo and enable corresponding feature This CL bumps to the latest Rust-scudo version and re-enables the corresponding feature, after it was disabled in crrev/c/3964927. The fix introduced in https://github.com/google/rust-scudo/pull/6 was submitted and is part of the 0.1.3 release of scudo. BUG=None TEST=health-check Change-Id: I9c658cde9ea2d4cdf0d03110e2d015c8339e5267 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3973490 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-10-24 12:54:18 +00:00
"quote 1.0.21",
"syn 1.0.103",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
]
[[package]]
name = "wmi"
version = "0.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "757a458f9bfab0542c11feed99bd492cbe23add50515bd8eecf8c6973673d32d"
dependencies = [
"chrono",
"log",
"serde",
"thiserror",
"widestring",
"winapi",
]
[[package]]
name = "x86_64"
version = "0.1.0"
dependencies = [
"acpi_tables",
"anyhow",
"arch",
"base",
"cfg-if",
"chrono",
arch: split fdt code into its own crate This will let the hypervisor crate use types and functions from the new cros_fdt crate (it could not depend on arch, since that would cause a circular dependency). No functional change, just code movement. BUG=b:253416076 TEST=cargo build TEST=cargo build --target=aarch64-unknown-linux-gnu Change-Id: I62d906941867c45f1b77ff1db6923d915ce2123e Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3965088 Reviewed-by: Steven Moreland <smoreland@google.com> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2022-10-18 19:50:50 +00:00
"cros_fdt",
Add Cargo.lock files to version control again We originally removed it because we had frequent merge conflicts and all downstream projects were doing their own pinning already. We also had CI issues because ChromeOS changes could trigger Cargo.lock changes in crosvm back then. The new Cargo.lock format should ease the merge conflicts and we no longer have issues with external changes triggering changes in our Cargo.lock. So let's bring it back in. This will allow us to judge the impact of changing third party dependencies and gives us a chance to implement a special review process. BUG=b:240435583 TEST=CQ Change-Id: Ie53e5616cc98d7e50a84f3c0a91902dd539f2520 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3795655 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com>
2022-08-01 22:42:35 +00:00
"data_model",
"devices",
"gdbstub_arch",
"hypervisor",
"kernel_cmdline",
"kernel_loader",
"libc",
"minijail",
"once_cell",
"remain",
"resources",
"sync",
"thiserror",
"vm_control",
"vm_memory",
]
Reference in a new issue Copy permalink