From 20df9df706f2c35b37d623c569c6110fc2f402cb Mon Sep 17 00:00:00 2001 From: Dan Andresan Date: Mon, 11 May 2020 14:43:06 +0200 Subject: Add vfio-pci, igb_uio limitations Change-Id: I7fc1d0c47bd4b949c5246c5fa1073676f5eebc67 --- .../doc/known_bugs_and_limitations.xml | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml index ce9e9e0..66c54d7 100644 --- a/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml +++ b/doc/book-enea-nfv-access-release-info/doc/known_bugs_and_limitations.xml @@ -92,6 +92,20 @@ storage devices. + + LXCR-9992Due to the way VFIO works, there are + certain limitations regarding which devices can be used with VFIO. Mainly, it + comes down to how IOMMU groups work. Any Virtual Function device can + be used with VFIO on its own, however, physical devices will require either + all ports to be bound to VFIO, or only some of them bound while others not + bound to anything at all. + + If UEFI secure boot is enabled, the Linux kernel may disallow the + use of UIO on the system. Therefore, devices intended for use by the DPDK should be + bound to the vfio-pci kernel module rather than the + igb_uio. + + PDF navigation: When using links to open other PDFs, or jump to another place in the same PDF, jumping @@ -106,4 +120,4 @@ - \ No newline at end of file + -- cgit v1.2.3-54-g00ecf