External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-11-05 03:21:13 +00:00
Code Issues Packages Projects Releases Wiki Activity
751a302050
cloud-hypervisor/pci/Cargo.toml

27 lines
733 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]
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" }
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" }
vfio: Switch to the vfio-ioctls crate ch branch Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-12 14:36:07 +00:00
vfio-ioctls = { git = "https://github.com/cloud-hypervisor/vfio-ioctls", branch = "ch" }
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
vmm-sys-util = ">=0.3.1"
build(deps): bump libc from 0.2.71 to 0.2.72 Bumps [libc](https://github.com/rust-lang/libc) from 0.2.71 to 0.2.72. - [Release notes](https://github.com/rust-lang/libc/releases) - [Commits](https://github.com/rust-lang/libc/compare/0.2.71...0.2.72) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-07-07 23:35:09 +00:00
libc = "0.2.72"
build(deps): bump log from 0.4.8 to 0.4.11 Bumps [log](https://github.com/rust-lang/log) from 0.4.8 to 0.4.11. - [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.8...0.4.11) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-07-16 01:25:13 +00:00
log = "0.4.11"
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(deps): bump vm-memory from 0.2.0 to 0.2.1 Bumps [vm-memory](https://github.com/rust-vmm/vm-memory) from 0.2.0 to 0.2.1. - [Release notes](https://github.com/rust-vmm/vm-memory/releases) - [Changelog](https://github.com/rust-vmm/vm-memory/blob/v0.2.1/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/vm-memory/compare/v0.2.0...v0.2.1) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-05-28 15:06:54 +00:00
vm-memory = "0.2.1"
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]
git = "https://github.com/rust-vmm/vfio-bindings"
features = ["fam-wrappers"]
Reference in New Issue Copy Permalink