From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1596] devbind no longer works unless VFIO_UNSAFE is enabled
Date: Wed, 11 Dec 2024 23:48:40 +0000 [thread overview]
Message-ID: <bug-1596-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]
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: dev@dpdk.org
Reporter: stephen@networkplumber.org
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 <fidaullah.noonari@emumba.com>
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.
Signed-off-by: Fidaullah Noonari <fidaullah.noonari@emumba.com>
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3715 bytes --]
reply other threads:[~2024-12-11 23:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-1596-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).