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
d17fa784bc
cloud-hypervisor/vfio/Cargo.toml

26 lines
591 B
TOML
Raw Normal View History

vfio: VFIO API wrappers and helpers The Virtual Function I/O (VFIO) kernel subsystem exposes a vast and relatively complex userspace API. This commit abstracts and simplifies this API into both an internal and external API. The external API is to be consumed by VFIO device implementation through the VfioDevice structure. A VfioDevice instance can: - Enable and disable all interrupts (INTX, MSI and MSI-X) on the underlying VFIO device. - Read and write all of the VFIO device memory regions. - Set the system's IOMMU tables for the underlying device. Signed-off-by: Zhang, Xiong Y <xiong.y.zhang@intel.com> Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-06-13 20:13:35 +00:00
[package]
name = "vfio"
version = "0.0.1"
authors = ["The Cloud Hypervisor Authors"]
[dependencies]
vm-virtio, vmm, vfio: Store GuestMemoryMmap in an Arc<ArcSwap<T>> This allows us to change the memory map that is being used by the devices via an atomic swap (by replacing the map with another one). The ArcSwap provides the mechanism for atomically swapping from to another whilst still giving good read performace. It is inside an Arc so that we can use a single ArcSwap for all users. Not covered by this change is replacing the GuestMemoryMmap itself. This change also removes some vertical whitespace from use blocks in the files that this commit also changed. Vertical whitespace was being used inconsistently and broke rustfmt's behaviour of ordering the imports as it would only do it within the block. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-31 10:49:11 +00:00
arc-swap = ">=0.4.4"
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"
vfio: Initial PCI support This brings the initial PCI support to the VFIO crate. The VfioPciDevice is the main structure and holds an inner VfioDevice. VfioPciDevice implements the PCI trait, leaving the IRQ assignments empty as this will be driven by both the guest and the VFIO PCI device, not by the VMM. As we must trap BAR programming from the guest (We don't want to program the actual device with guest addresses), we use our local PCI configuration cache to read and write BARs. Signed-off-by: Zhang, Xiong Y <xiong.y.zhang@intel.com> Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-07-15 07:50:55 +00:00
devices = { path = "../devices" }
cargo: Bump the kvm and vmm-sys-util crates Since the kvm crates now depend on vmm-sys-util, the bump must be atomic. The kvm-bindings and ioctls 0.2.0 and 0.4.0 crates come with a few API changes, one of them being the use of a kvm_ioctls specific error type. Porting our code to that type makes for a fairly large diff stat. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-11-29 15:36:33 +00:00
kvm-bindings = "0.2.0"
build(deps): bump kvm-ioctls from 0.4.0 to 0.5.0 Bumps [kvm-ioctls](https://github.com/rust-vmm/kvm-ioctls) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/rust-vmm/kvm-ioctls/releases) - [Changelog](https://github.com/rust-vmm/kvm-ioctls/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-vmm/kvm-ioctls/compare/v0.4.0...v0.5.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
2020-01-29 09:53:56 +00:00
kvm-ioctls = "0.5.0"
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
libc = "0.2.60"
log = "0.4.8"
vfio: Initial PCI support This brings the initial PCI support to the VFIO crate. The VfioPciDevice is the main structure and holds an inner VfioDevice. VfioPciDevice implements the PCI trait, leaving the IRQ assignments empty as this will be driven by both the guest and the VFIO PCI device, not by the VMM. As we must trap BAR programming from the guest (We don't want to program the actual device with guest addresses), we use our local PCI configuration cache to read and write BARs. Signed-off-by: Zhang, Xiong Y <xiong.y.zhang@intel.com> Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-07-15 07:50:55 +00:00
pci = { path = "../pci" }
vm-allocator = { path = "../vm-allocator" }
vfio: Create VFIO implementation of ExternalDmaMapping With this implementation of the trait ExternalDmaMapping, we now have the tool to provide to the virtual IOMMU to trigger the map/unmap on behalf of the guest. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-07 17:48:44 +00:00
vm-device = { path = "../vm-device" }
vmm: Port to latest vmm-sys-util The signal handling for vCPU signals has changed in the latest release so switch to the new API. Signed-off-by: Rob Bradford <robert.bradford@intel.com>
2019-12-11 13:02:07 +00:00
vmm-sys-util = ">=0.3.1"
vfio: VFIO API wrappers and helpers The Virtual Function I/O (VFIO) kernel subsystem exposes a vast and relatively complex userspace API. This commit abstracts and simplifies this API into both an internal and external API. The external API is to be consumed by VFIO device implementation through the VfioDevice structure. A VfioDevice instance can: - Enable and disable all interrupts (INTX, MSI and MSI-X) on the underlying VFIO device. - Read and write all of the VFIO device memory regions. - Set the system's IOMMU tables for the underlying device. Signed-off-by: Zhang, Xiong Y <xiong.y.zhang@intel.com> Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com> Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-06-13 20:13:35 +00:00
[dependencies.vm-memory]
git = "https://github.com/rust-vmm/vm-memory"
features = ["backend-mmap"]
vfio: Use the vfio-binding FAM wrappers It's less unsafe and makes the code more readable. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2020-01-24 17:02:15 +00:00
[dependencies.vfio-bindings]
git = "https://github.com/rust-vmm/vfio-bindings"
features = ["fam-wrappers"]
Reference in New Issue Copy Permalink