cloud-hypervisor/virtio-devices/src/transport/mod.rs

// Copyright © 2019 Intel Corporation
//
// SPDX-License-Identifier: Apache-2.0

use vmm_sys_util::eventfd::EventFd;
mod pci_common_config;
mod pci_device;
pub use pci_common_config::VirtioPciCommonConfig;
pub use pci_device::VirtioPciDevice;

pub trait VirtioTransport {
    fn ioeventfds(&self, base_addr: u64) -> Vec<(&EventFd, u64)>;
}
cloud-hypervisor: Add proper licensing Add the BSD and Apache license. Make all crosvm references point to the BSD license. Add the right copyrights and identifier to our VMM code. Add Intel copyright to the vm-virtio and pci crates. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-05-08 10:22:53 +00:00			`// Copyright © 2019 Intel Corporation`
			`//`
			`// SPDX-License-Identifier: Apache-2.0`
vm-virtio: Add PCI transport support Copied from crosvm 107edb3e with one main modification: VirtioPciDevice implements BusDevice. We need this modification because it is the only way for us to be able to add a VirtioPciDevice to the MMIO bus. Bus insertion takes a BusDevice. The fact that VirtioPciDevice implements PciDevice which itself implements BusDevice does not mean that Rust will automatically downcast a VirtioPciDevice into a BusDevice. crosvm works around that issue by having the PCI, virtio and BusDevice implementations in the same crate. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-04-18 17:32:41 +00:00
vm-virtio: Create new VirtioTransport trait to abstract ioeventfds In order to group together some functions that can be shared across virtio transport layers, this commit introduces a new trait called VirtioTransport. The first function of this trait being ioeventfds() as it is needed from both virtio-mmio and virtio-pci devices, represented by MmioDevice and VirtioPciDevice structures respectively. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2019-10-30 18:03:02 +00:00			`use vmm_sys_util::eventfd::EventFd;`
vm-virtio: Add PCI transport support Copied from crosvm 107edb3e with one main modification: VirtioPciDevice implements BusDevice. We need this modification because it is the only way for us to be able to add a VirtioPciDevice to the MMIO bus. Bus insertion takes a BusDevice. The fact that VirtioPciDevice implements PciDevice which itself implements BusDevice does not mean that Rust will automatically downcast a VirtioPciDevice into a BusDevice. crosvm works around that issue by having the PCI, virtio and BusDevice implementations in the same crate. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com> 2019-04-18 17:32:41 +00:00			`mod pci_common_config;`
			`mod pci_device;`
			`pub use pci_common_config::VirtioPciCommonConfig;`
			`pub use pci_device::VirtioPciDevice;`
vm-virtio: Add MMIO transport Derived from the crosvm code at 5656c124af2bb956dba19e409a269ca588c685e3 and adapted to work within cloud-hypervisor: Main differences: * Interrupt handling is done via a VirtioInterrupt turned into a devices::Interrupt * GuestMemory -> GuestMemoryMmap * Differences in read/write for BusDevice * Different crates for EventFd and GuestAddress Signed-off-by: Rob Bradford <robert.bradford@intel.com> 2019-09-11 16:20:12 +00:00
vm-virtio: Create new VirtioTransport trait to abstract ioeventfds In order to group together some functions that can be shared across virtio transport layers, this commit introduces a new trait called VirtioTransport. The first function of this trait being ioeventfds() as it is needed from both virtio-mmio and virtio-pci devices, represented by MmioDevice and VirtioPciDevice structures respectively. Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com> 2019-10-30 18:03:02 +00:00			`pub trait VirtioTransport {`
			`fn ioeventfds(&self, base_addr: u64) -> Vec<(&EventFd, u64)>;`
			`}`