External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-07-05 01:12:36 +00:00
Code Issues Packages Projects Releases Wiki Activity
fa7a000dbe
cloud-hypervisor/block/Cargo.toml

28 lines
731 B
TOML
Raw Normal View History

vhost_user_block, virtio-devices, block_util: Extract common block code Extract the code that is used by vhost_user_block from the virtio-devices crate to remove the dependencies on unrequired functionality such as the virtio transports. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-14 09:43:33 +00:00
[package]
block: merge qcow, vhdx and block_util into block crate This commit merges crates `qcow`, `vhdx` and `block_util` into the crate `block`, which can allow `qcow` to use functions from `block_util` without introducing a circular crate dependency. This commit is based on crosvm implementation: https://chromium.googlesource.com/crosvm/crosvm/+/f2eecc4152eca8d395566cffa2c102ec090a152d Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
2023-07-12 02:24:28 +00:00
name = "block"
vhost_user_block, virtio-devices, block_util: Extract common block code Extract the code that is used by vhost_user_block from the virtio-devices crate to remove the dependencies on unrequired functionality such as the virtio transports. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-14 09:43:33 +00:00
version = "0.1.0"
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"
block: merge qcow, vhdx and block_util into block crate This commit merges crates `qcow`, `vhdx` and `block_util` into the crate `block`, which can allow `qcow` to use functions from `block_util` without introducing a circular crate dependency. This commit is based on crosvm implementation: https://chromium.googlesource.com/crosvm/crosvm/+/f2eecc4152eca8d395566cffa2c102ec090a152d Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
2023-07-12 02:24:28 +00:00
authors = ["The Cloud Hypervisor Authors", "The Chromium OS Authors"]
vhost_user_block, virtio-devices, block_util: Extract common block code Extract the code that is used by vhost_user_block from the virtio-devices crate to remove the dependencies on unrequired functionality such as the virtio transports. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-14 09:43:33 +00:00
io_uring: Add new feature gate By adding a new io_uring feature gate, we let the user the possibility to choose if he wants to enable the io_uring improvements or not. Since the io_uring feature depends on the availability on recent host kernels, it's better if we leave it off for now. As soon as our CI will have support for a kernel 5.6 with all the features needed from io_uring, we'll enable this feature gate permanently. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-08-03 06:32:28 +00:00
[features]
default = []
build: Allow disabling io_uring This gives users the chance to reduce the number of dependencies included, which is generally good practice and also reduces code size. Furthermore, `io_uring` specifically is a strong contender for something one may wish to disable due to the syscall API's many security issues[1] [1]: https://security.googleblog.com/2023/06/learnings-from-kctf-vrps-42-linux.html Signed-off-by: Manish Goregaokar <manishsmail@gmail.com>
2023-07-10 09:55:55 +00:00
io_uring = ["dep:io-uring"]
io_uring: Add new feature gate By adding a new io_uring feature gate, we let the user the possibility to choose if he wants to enable the io_uring improvements or not. Since the io_uring feature depends on the availability on recent host kernels, it's better if we leave it off for now. As soon as our CI will have support for a kernel 5.6 with all the features needed from io_uring, we'll enable this feature gate permanently. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-08-03 06:32:28 +00:00
vhost_user_block, virtio-devices, block_util: Extract common block code Extract the code that is used by vhost_user_block from the virtio-devices crate to remove the dependencies on unrequired functionality such as the virtio transports. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2020-07-14 09:43:33 +00:00
[dependencies]
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"
block: Replace use of crc32c crate with crc-any According to crates.io the crc-any crate is actively maintained which avoids issues with the crc32c crate and the nightly compiler. Fixes: #6168 Signed-off-by: Rob Bradford <rbradford@rivosinc.com>
2024-02-06 20:48:47 +00:00
crc-any = "2.4.4"
build: Bump io-uring from 0.6.1 to 0.6.2 Bumps [io-uring](https://github.com/tokio-rs/io-uring) from 0.6.1 to 0.6.2. - [Commits](https://github.com/tokio-rs/io-uring/commits) --- updated-dependencies: - dependency-name: io-uring dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-07 22:30:53 +00:00
io-uring = { version = "0.6.2", optional = true }
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 log from 0.4.17 to 0.4.20 Bumps [log](https://github.com/rust-lang/log) from 0.4.17 to 0.4.20. - [Release notes](https://github.com/rust-lang/log/releases) - [Changelog](https://github.com/rust-lang/log/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/log/compare/0.4.17...0.4.20) --- updated-dependencies: - dependency-name: log dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-11-23 23:47:38 +00:00
log = "0.4.20"
build: Bump remain from 0.2.10 to 0.2.11 Bumps [remain](https://github.com/dtolnay/remain) from 0.2.10 to 0.2.11. - [Release notes](https://github.com/dtolnay/remain/releases) - [Commits](https://github.com/dtolnay/remain/compare/0.2.10...0.2.11) --- updated-dependencies: - dependency-name: remain dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-08-02 23:05:18 +00:00
remain = "0.2.11"
build: Bump smallvec from 1.13.1 to 1.13.2 Bumps [smallvec](https://github.com/servo/rust-smallvec) from 1.13.1 to 1.13.2. - [Release notes](https://github.com/servo/rust-smallvec/releases) - [Commits](https://github.com/servo/rust-smallvec/compare/v1.13.1...v1.13.2) --- updated-dependencies: - dependency-name: smallvec dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-03-26 23:48:52 +00:00
smallvec = "1.13.2"
build: Bump thiserror from 1.0.40 to 1.0.52 Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.40 to 1.0.52. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](https://github.com/dtolnay/thiserror/compare/1.0.40...1.0.52) --- updated-dependencies: - dependency-name: thiserror dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2023-12-29 23:11:34 +00:00
thiserror = "1.0.52"
block: merge qcow, vhdx and block_util into block crate This commit merges crates `qcow`, `vhdx` and `block_util` into the crate `block`, which can allow `qcow` to use functions from `block_util` without introducing a circular crate dependency. This commit is based on crosvm implementation: https://chromium.googlesource.com/crosvm/crosvm/+/f2eecc4152eca8d395566cffa2c102ec090a152d Signed-off-by: Yu Li <liyu.yukiteru@bytedance.com>
2023-07-12 02:24:28 +00:00
uuid = { version = "1.3.4", features = ["v4"] }
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
versionize = "0.2.0"
versionize_derive = "0.1.6"
build: Bump virtio-bindings from 0.1.0 to 0.2.0 Bumps [virtio-bindings](https://github.com/rust-vmm/vm-virtio) from 0.1.0 to 0.2.0. - [Release notes](https://github.com/rust-vmm/vm-virtio/releases) - [Commits](https://github.com/rust-vmm/vm-virtio/compare/virtio-queue-v0.1.0...virtio-bindings-v0.2.0) --- updated-dependencies: - dependency-name: virtio-bindings dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-21 23:58:46 +00:00
virtio-bindings = { version = "0.2.0", features = ["virtio-v5_0_0"] }
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
virtio-queue = "0.11.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-atomic", "backend-bitmap"] }
block_util: Add utilities to support io_uring Creates a dedicated function relying on io_uring crate to execute io_uring specific requests. Also creates a function for checking io_uring support on the host. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-07-27 13:58:53 +00:00
vm-virtio = { path = "../vm-virtio" }
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 = "0.12.1"
Reference in New Issue Copy Permalink