External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-11-10 05:40:10 +00:00
Code Issues Packages Projects Releases Wiki Activity
1aeaee221d
cloud-hypervisor/arch/Cargo.toml

29 lines
812 B
TOML
Raw Normal View History

cloud-hypervisor: Add the architecture crates Both crates are based on Firecracker commit 9cdb5b2. They are ported to the new memory model and tests have been fixed accordingly. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-25 21:53:01 +00:00
[package]
name = "arch"
version = "0.1.0"
authors = ["The Chromium OS Authors"]
build: migrate to Rust 2021 edition Rust 2021 edition has a few improvements over the 2018 edition. Migrate the project to 2021 edition by following recommended migration steps. Luckily, the code itself doesn't require fixing. Bump MSRV to 1.56 as it is required by the 2021 edition. Also fix the clap build dependency to make Cloud Hypervisor build again. Signed-off-by: Wei Liu <liuwe@microsoft.com>
2022-04-08 15:11:04 +00:00
edition = "2021"
cloud-hypervisor: Add the architecture crates Both crates are based on Firecracker commit 9cdb5b2. They are ported to the new memory model and tests have been fixed accordingly. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-25 21:53:01 +00:00
vmm, arch, devices: Put ACPI support behind a default feature Put the ACPI support behind a feature and ensure that the code compiles without that feature by adding an extra build to Travis. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-03 13:54:06 +00:00
[features]
build: Really make the acpi feature disableable The command "cargo build --no-default-features" does not recursively disable the default features across the workspace. Instead add an acpi feature at the top-level, making it default, and then make that feature conditional on all the crate acpi features. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-05 15:29:55 +00:00
default = []
vmm: Add a feature flag for SEV-SNP support This feature flag gates the development for SEV-SNP enabled guest. Also add a helper function to identify if SNP should be enabled for the guest. Signed-off-by: Jinank Jain <jinankjain@microsoft.com>
2022-10-11 09:58:00 +00:00
sev_snp = []
tdx: Add "tdx" feature with an empty module inside arch to implement Add the skeleton of the "tdx" feature with a module ready inside the arch crate to store implementation details. TEST=cargo build --features="tdx" Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-02-03 10:02:18 +00:00
tdx = []
vmm, arch, devices: Put ACPI support behind a default feature Put the ACPI support behind a feature and ensure that the code compiles without that feature by adding an extra build to Travis. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-09-03 13:54:06 +00:00
cloud-hypervisor: Add the architecture crates Both crates are based on Firecracker commit 9cdb5b2. They are ported to the new memory model and tests have been fixed accordingly. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-25 21:53:01 +00:00
[dependencies]
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
anyhow = "1.0.81"
build: Bump byteorder from 1.4.3 to 1.5.0 Bumps [byteorder](https://github.com/BurntSushi/byteorder) from 1.4.3 to 1.5.0. - [Changelog](https://github.com/BurntSushi/byteorder/blob/master/CHANGELOG.md) - [Commits](https://github.com/BurntSushi/byteorder/compare/1.4.3...1.5.0) --- updated-dependencies: - dependency-name: byteorder dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-29 23:33:33 +00:00
byteorder = "1.5.0"
arch, pci, vmm: Initial switch to the hypervisor crate Start moving the vmm, arch and pci crates to being hypervisor agnostic by using the hypervisor trait and abstractions. This is not a complete switch and there are still some remaining KVM dependencies. Signed-off-by: Muminul Islam <muislam@microsoft.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-06-02 02:29:54 +00:00
hypervisor = { path = "../hypervisor" }
build: Bump libc from 0.2.151 to 0.2.153 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.151 to 0.2.153. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.151...0.2.153) --- updated-dependencies: - dependency-name: libc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-02-07 23:15:53 +00:00
libc = "0.2.153"
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
linux-loader = { version = "0.11.0", features = ["elf", "bzimage", "pe"] }
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
log = "0.4.21"
serde = { version = "1.0.197", features = ["rc", "derive"] }
thiserror = "1.0.58"
uuid = "1.8.0"
build: Bump vm-memory from 0.14.0 to 0.14.1 Bumps [vm-memory](https://github.com/rust-vmm/vm-memory) from 0.14.0 to 0.14.1. - [Release notes](https://github.com/rust-vmm/vm-memory/releases) - [Changelog](https://github.com/rust-vmm/vm-memory/blob/v0.14.1/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/vm-memory/compare/v0.14.0...v0.14.1) --- updated-dependencies: - dependency-name: vm-memory dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-04-02 23:22:11 +00:00
vm-memory = { version = "0.14.1", features = ["backend-mmap", "backend-bitmap"] }
arch: AArch64: implement save/restore for GICv3 This commit implements the save/restore for GICv3. Signed-off-by: Henry Wang <Henry.Wang@arm.com>
2020-09-04 01:52:05 +00:00
vm-migration = { path = "../vm-migration" }
build: Bump vmm-sys-util crate and its consumers This patch bumps the following crates, including `kvm-bindings@0.7.0`*, `kvm-ioctls@0.16.0`**, `linux-loader@0.11.0`, `versionize@0.2.0`, `versionize_derive@0.1.6`***, `vhost@0.10.0`, `vhost-user-backend@0.13.1`, `virtio-queue@0.11.0`, `vm-memory@0.14.0`, `vmm-sys-util@0.12.1`, and the latest of `vfio-bindings`, `vfio-ioctls`, `mshv-bindings`,`mshv-ioctls`, and `vfio-user`. * A fork of the `kvm-bindings` crate is being used to support serialization of various structs for migration [1]. Also, code changes are made to accommodate the updated `struct xsave` from the Linux kernel. Note: these changes related to `struct xsave` break live-upgrade. ** The new `kvm-ioctls` crate introduced breaking changes for the `get/set_one_reg` API on `aarch64` [2], so code changes are made to the new APIs. *** A fork of the `versionize_derive` crate is being used to support versionize on packed structs [3]. [1] https://github.com/cloud-hypervisor/kvm-bindings/tree/ch-v0.7.0 [2] https://github.com/rust-vmm/kvm-ioctls/pull/223 [3] https://github.com/cloud-hypervisor/versionize_derive/tree/ch-0.1.6 Fixes: #6072 Signed-off-by: Bo Chen <chen.bo@intel.com>
2024-01-23 17:29:40 +00:00
vmm-sys-util = { version = "0.12.1", features = ["with-serde"] }
cloud-hypervisor: Add the architecture crates Both crates are based on Firecracker commit 9cdb5b2. They are ported to the new memory model and tests have been fixed accordingly. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-02-25 21:53:01 +00:00
arch: Add logging for FDT debugging on AArch64 To debug the FDT (Flattened Device Tree), we usually need to modify source code to save the generted DTB data to disk, and use 'dtc' command to decode the binary file into a text file to analyze. It would be ideal if the FDT content can be seen in log. This commit makes it real by: - Introducing 'fdt' crate for parsing FDT. - Printing the content of the FDT in tree view. The parsing and printing only happen when Debug level logging enabled. Signed-off-by: Michael Zhao <michael.zhao@arm.com>
2021-06-16 04:45:32 +00:00
[target.'cfg(target_arch = "aarch64")'.dependencies]
build: Bulk update dependencies Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-04-06 07:47:54 +00:00
fdt_parser = { version = "0.1.5", package = "fdt" }
build: update Cargo for rust-vmm branch renames The rust-vmm crates we're pulling from git have renamed their main branches. We need to update the branch names we're giving to Cargo, or people who don't have these dependencies cached will get errors like this when trying to build: error: failed to get `vm-fdt` as a dependency of package `arch v0.1.0 (/home/src/cloud-hypervisor/arch)` Caused by: failed to load source for dependency `vm-fdt` Caused by: Unable to update https://github.com/rust-vmm/vm-fdt?branch=master#031572a6 Caused by: object not found - no match for id (031572a6edc2f566a7278f1e17088fc5308d27ab); class=Odb (9); code=NotFound (-3) Signed-off-by: Alyssa Ross <hi@alyssa.is>
2021-09-02 08:44:25 +00:00
vm-fdt = { git = "https://github.com/rust-vmm/vm-fdt", branch = "main" }
Reference in New Issue Copy Permalink