Public bug reported:

Hi,
for certain cases a user might want to use VFIO in NO IOMMU mode.
This only enables it to be an option, it doesn't change things unless 
"enable_unsafe_noiommu_mode" is set. See this reference: 
https://patchwork.kernel.org/patch/7906971/ for more details.

This is used for some setups of DPDK see this http://dpdk-
guide.gitlab.io/dpdk-guide/setup/binding.html#vfio-no-iommu

Usually the reason to pick vfio over uio is the isolation. But there are
some cases where vfio is required for extra features but can't work
unless NO-IOMMU mode is used.

I watched the topic a while checking if there is some major "oh crap
what have we done" but there was none. An since by only enabling it in
the kernel it shouldn't change a lot I wanted to ask if you could enable
this config in the kernel for Z*.

Technically it would be nice to get it in Yakkety as well, but I think
we should be fine only working forward and enabling it in the Z release.

** Affects: dpdk (Ubuntu)
     Importance: Medium
         Status: Incomplete

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete

** Also affects: dpdk (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: dpdk (Ubuntu)
       Status: New => Triaged

** Changed in: dpdk (Ubuntu)
       Status: Triaged => Incomplete

** Changed in: dpdk (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634050

Title:
  Please enable CONFIG_VFIO_NOIOMMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1634050/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to