b3db2a65ea
Previously we used VFIO if only the vfio-pci kernel module was loaded, which is different from what our setup.sh script did. On a fairly usual system configuration, setup.sh could have bound devices to UIO, but SPDK would still try to map memory to an (empty) DPDK VFIO container just because its fd was available. That would fail obviously. setup.sh checks for IOMMU presence in order to use vfio-pci and SPDK should probably do the same. We could check the kernel driver of each attached PCI device, but there's no chance right now of supporting both UIO and VFIO devices at the same time with IOMMU passthrough. That's not a reasonable configuration anyway. To keep things simple, we just add a single check on vtophys initialization. Fixes #462 Change-Id: Ica653f117743be322291a1b7e37ed00e34ef5035 Signed-off-by: Darek Stojaczyk <dariusz.stojaczyk@intel.com> Reviewed-on: https://review.gerrithub.io/432518 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: <wuzhouhui@kingsoft.com> |
||
|---|---|---|
| .. | ||
| env_internal.h | ||
| env.c | ||
| env.mk | ||
| init.c | ||
| Makefile | ||
| memory.c | ||
| pci_ioat.c | ||
| pci_nvme.c | ||
| pci_virtio.c | ||
| pci.c | ||
| threads.c | ||
| vtophys.c | ||