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

21 lines
508 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]
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
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 07:50:55 +00: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 11:02:17 +00: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 20:13:35 +00: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 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" }
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 07:41:13 +00: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 07:50:55 +00:00
vm-allocator = { path = "../vm-allocator" }
Cargo: Move to crates.io vmm-sys-util Use the newly published 0.1.1 version. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-10-08 11:43:28 +00: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 20:13:35 +00:00
[dependencies.vm-memory]
git = "https://github.com/rust-vmm/vm-memory"
features = ["backend-mmap"]
Reference in New Issue Copy Permalink