Skip to contentSkip to conversation

devbind no longer works unless VFIO_UNSAFE is enabled

DPDK/core Bug 1596 [email protected] 1 participant 1 message Dec 11, 2024

lore
Share & tools
lore

[email protected]

author Acked-by Bruce Richardson
#0 lore raw

https://bugs.dpdk.org/show_bug.cgi?id=1596

            Bug ID: 1596
           Summary: devbind no longer works unless VFIO_UNSAFE is enabled
           Product: DPDK
           Version: 24.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: core
          Assignee: [email protected]
          Reporter: [email protected]

Target Milestone: ---

Debian (and probably lots of other distributions), do not enable unsafe VFIO option (CONFIG_VFIO_NOIOMMU). If that is true, then the module parameter does not exist.

This causes DPDK devbind to fail:
Error: failed to check unsafe noiommu mode - Cannot open /sys/module/vfio/parameters/enable_unsafe_noiommu_mode: [Errno 2] No such file or directory: '/sys/module/vfio/parameters/enable_unsafe_noiommu_mode'

This regression is caused by the commit.

commit 6ca0f1c8450d6e28926cad33c6500ad487f4cfdb

Author: Fidaullah Noonari <[email protected]>
Date:   Wed Oct 2 11:13:12 2024 -0700

usertools/devbind: support VFIO non-IOMMU mode

This patch adds noiommu option to dpdk-devbind. If the no IOMMU is detected, then if noiommu flag is set the vfio-pci unsafe_noiommu_mode flag is set.

Signature · 2 lines
You are receiving this mail because:
You are the assignee for the bug.