cloud-hypervisor/pci/Cargo.toml

[package]
name = "pci"
version = "0.1.0"
authors = ["Samuel Ortiz <sameo@linux.intel.com>"]
edition = "2018"

[dependencies]
anyhow = "1.0"
byteorder = "1.3.4"
devices = { path = "../devices" }
libc = "0.2.69"
log = "0.4.8"
serde = {version = ">=1.0.27", features = ["rc"] }
serde_derive = ">=1.0.27"
serde_json = ">=1.0.9"
vm-allocator = { path = "../vm-allocator" }
vm-device = { path = "../vm-device" }
vm-memory = "0.2.0"
vm-migration = { path = "../vm-migration" }
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]`
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			`anyhow = "1.0"`
build(deps): bump byteorder from 1.3.2 to 1.3.4 Bumps [byteorder](https://github.com/BurntSushi/byteorder) from 1.3.2 to 1.3.4. - [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.3.2...1.3.4) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> 2020-02-07 13:44:37 +00:00			`byteorder = "1.3.4"`
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			`devices = { path = "../devices" }`
build(deps): bump libc from 0.2.68 to 0.2.69 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.68 to 0.2.69. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.68...0.2.69) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> 2020-04-13 23:33:46 +00:00			`libc = "0.2.69"`
build: Bulk update dependencies Update all dependencies with "cargo upgrade" with the exception of vmm-sys-utils which needs some extra porting work. Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2019-08-02 11:02:17 +00:00			`log = "0.4.8"`
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			`serde = {version = ">=1.0.27", features = ["rc"] }`
			`serde_derive = ">=1.0.27"`
			`serde_json = ">=1.0.9"`
			`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: Bump vm-memory and linux-loader dependencies linux-loader depends on vm-memory so must be updated at the same time. Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2020-03-23 13:54:34 +00:00			`vm-memory = "0.2.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" }`