** Also affects: linux (Ubuntu Z-series)
   Importance: Undecided
       Status: New

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

** Changed in: linux (Ubuntu Z-series)
       Status: New => In Progress

** Changed in: linux (Ubuntu Z-series)
     Assignee: (unassigned) => Tim Gardner (timg-tpi)

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.


Status in dpdk package in Ubuntu:
Status in linux package in Ubuntu:
Status in dpdk source package in z-series:
Status in linux source package in z-series:
  In Progress

Bug description:
  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-

  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

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to