External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2025-01-13 16:05:15 +00:00
Code Issues Packages Projects Releases Wiki Activity
cloud-hypervisor/vfio/Cargo.toml

22 lines
548 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 22:13:35 +02:00
[package]
name = "vfio"
version = "0.0.1"
authors = ["The Cloud Hypervisor Authors"]
[dependencies]
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 12:02:17 +01:00
byteorder = "1.3.2"
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 09:50:55 +02:00
devices = { path = "../devices" }
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 12:02:17 +01:00
kvm-bindings = "0.1.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 22:13:35 +02:00
kvm-ioctls = { git = "https://github.com/rust-vmm/kvm-ioctls", branch = "master" }
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 12:02:17 +01: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 09:50:55 +02:00
pci = { path = "../pci" }
vfio: Move vfio-bindings to crates.io And remove our local vfio-bindings code. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-10 09:41:13 +02:00
vfio-bindings = "0.1.0"
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 09:50:55 +02:00
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 10:48:44 -07:00
vm-device = { path = "../vm-device" }
cargo: Update to the latest kvm-ioctls version We need to rely on the latest kvm-ioctls version to benefit from the recent addition of unregister_ioevent(), allowing us to detach a previously registered eventfd to a PIO or MMIO guest address. Because of this update, we had to modify the current constraint we had on the vmm-sys-util crate, using ">= 0.1.1" instead of being strictly tied to "0.2.0". Once the dependency conflict resolved, this commit took care of fixing build issues caused by recent modification of kvm-ioctls relying on EventFd reference instead of RawFd. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
2019-10-30 09:38:38 -07:00
vmm-sys-util = ">=0.1.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 22:13:35 +02:00
[dependencies.vm-memory]
git = "https://github.com/rust-vmm/vm-memory"
features = ["backend-mmap"]
Reference in New Issue Copy Permalink