External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-11-05 11:31:14 +00:00
Code Issues Packages Projects Releases Wiki Activity
183605f9e1
cloud-hypervisor/pci/Cargo.toml

27 lines
673 B
TOML
Raw Normal View History

pci: Add minimal PCI host emulation crate This crate is based on the crosvm devices/src/pci implementation from 107edb3e We introduced a few changes: - This one is a standalone crate. The device crate does not carry any PCI specific bits. - Simplified PCI root configuration. We only carry a pointer to a PciConfiguration, not a wrapper around it. - Simplified BAR allocation API. All BARs from the PciDevice instance must be generated at once through the PciDevice.allocate_bars() method. - The PCI BARs are added to the MMIO bus from the PciRoot add_device() method. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-04-18 09:59:12 +00:00
[package]
name = "pci"
version = "0.1.0"
authors = ["Samuel Ortiz <sameo@linux.intel.com>"]
edition = "2018"
[dependencies]
build: bump anyhow from 1.0.42 to 1.0.43 Bumps [anyhow](https://github.com/dtolnay/anyhow) from 1.0.42 to 1.0.43. - [Release notes](https://github.com/dtolnay/anyhow/releases) - [Commits](https://github.com/dtolnay/anyhow/compare/1.0.42...1.0.43) --- updated-dependencies: - dependency-name: anyhow dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-16 23:55:42 +00:00
anyhow = "1.0.43"
build(deps): bump byteorder from 1.4.2 to 1.4.3 Bumps [byteorder](https://github.com/BurntSushi/byteorder) from 1.4.2 to 1.4.3. - [Release notes](https://github.com/BurntSushi/byteorder/releases) - [Changelog](https://github.com/BurntSushi/byteorder/blob/master/CHANGELOG.md) - [Commits](https://github.com/BurntSushi/byteorder/compare/1.4.2...1.4.3) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-03-10 12:36:39 +00:00
byteorder = "1.4.3"
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" }
pci, vmm: Move to upstream vfio-ioctls crate This commit moves both pci and vmm code from the internal vfio-ioctls crate to the upstream one from the rust-vmm project. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2021-02-23 14:01:31 +00:00
vfio-ioctls = { git = "https://github.com/rust-vmm/vfio-ioctls", branch = "master" }
pci: Add support for vfio-user PCI devices Taking advantage of the refactored VFIO code implement a new VfioUserPciDevice that wraps the client for vfio-user and exposes the BusDevice and PciDevice into the VMM. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-06-09 13:43:04 +00:00
vfio_user = { path = "../vfio_user" }
build: Use fixed versions in Cargo.toml files This doesn't really affect the build as we ship a Cargo.lock with fixed versions in. However for clarity it makes sense to use fixed versions throughout and let dependabot update them. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-08-06 09:11:40 +00:00
vmm-sys-util = "0.8.0"
build: bump libc from 0.2.99 to 0.2.100 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.99 to 0.2.100. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.99...0.2.100) --- updated-dependencies: - dependency-name: libc dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2021-08-24 05:08:50 +00:00
libc = "0.2.100"
build(deps): bump log from 0.4.13 to 0.4.14 Bumps [log](https://github.com/rust-lang/log) from 0.4.13 to 0.4.14. - [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.13...0.4.14) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2021-01-27 03:17:53 +00:00
log = "0.4.14"
pci: vfio: Cleanup error handling After the refactoring to split the common VFIO code out for vfio-user there were some inconsistencies in the error handling. Correct this so that the error is independent of the transport (hardware vs user) VFIO and migrate to anyhow/thiserror in the process. Some unused errors from earlier refactoring have also been removed. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-08-02 14:20:09 +00:00
thiserror = "1.0.26"
pci: Versionize PCI state Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-05-26 15:28:15 +00:00
versionize = "0.1.6"
versionize_derive = "0.1.4"
pci: Implement Snapshottable trait for MsixConfig In order to restore devices relying on MSI-X, the MsixConfig structure must be restored with the correct values. Additionally, the KVM routes must be restored so that interrupts can be delivered through KVM the way they were configured before the snapshot was taken. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-05-06 15:50:56 +00:00
vm-allocator = { path = "../vm-allocator" }
interrupt: Reorganize all interrupt management with InterruptManager Based on all the previous changes, we can at this point replace the entire interrupt management with the implementation of InterruptManager and InterruptSourceGroup traits. By using KvmInterruptManager from the DeviceManager, we can provide both VirtioPciDevice and VfioPciDevice a way to pick the kind of InterruptSourceGroup they want to create. Because they choose the type of interrupt to be MSI/MSI-X, they will be given a MsiInterruptGroup. Both MsixConfig and MsiConfig are responsible for the update of the GSI routes, which is why, by passing the MsiInterruptGroup to them, they can still perform the GSI route management without knowing implementation details. That's where the InterruptSourceGroup is powerful, as it provides a generic way to manage interrupt, no matter the type of interrupt and no matter which hypervisor might be in use. Once the full replacement has been achieved, both SystemAllocator and KVM specific dependencies can be removed. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-01-14 22:47:41 +00:00
vm-device = { path = "../vm-device" }
build: Move from patched vm-memory version to released version Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2021-08-06 07:46:17 +00:00
vm-memory = "0.6.0"
pci: Implement Snapshottable trait for MsixConfig In order to restore devices relying on MSI-X, the MsixConfig structure must be restored with the correct values. Additionally, the KVM routes must be restored so that interrupts can be delivered through KVM the way they were configured before the snapshot was taken. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2020-05-06 15:50:56 +00:00
vm-migration = { path = "../vm-migration" }
vfio: Move the PCI implementation to the PCI crate There is a much stronger PCI dependency from vfio_pci.rs than a VFIO one from pci/src/vfio.rs. It seems more natural to have the PCI specific VFIO implementation in the PCI crate rather than the other way around. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-08 14:50:39 +00:00
[dependencies.vfio-bindings]
pci: use vfio-bindings from crates.io This fixes `cargo vendor` throwing an error ``` $ cargo vendor error: failed to sync Caused by: found duplicate version of package `vfio-bindings v0.2.0` vendored from two sources: source 1: https://github.com/rust-vmm/vfio-bindings#f08cbcbf source 2: registry `https://github.com/rust-lang/crates.io-index` ``` Both sources are indeed same, the conflict is only cause by the different URLs. Signed-off-by: Anatol Belski <ab@php.net>
2020-08-05 11:53:09 +00:00
version = "0.2.0"
vfio: Move the PCI implementation to the PCI crate There is a much stronger PCI dependency from vfio_pci.rs than a VFIO one from pci/src/vfio.rs. It seems more natural to have the PCI specific VFIO implementation in the PCI crate rather than the other way around. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-08 14:50:39 +00:00
features = ["fam-wrappers"]
Reference in New Issue Copy Permalink