From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org, Robin Jarry <rjarry@redhat.com>
Subject: [PATCH v3 1/1] usertools/devbind: allow changing UID/GID for VFIO
Date: Wed, 27 Nov 2024 09:13:59 +0000 [thread overview]
Message-ID: <251f3e1bf71c3e873427708d566f677ecd50615c.1732698829.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <4cd0282dabfa59e715028ecf255468529655b487.1725285449.git.anatoly.burakov@intel.com>
Currently, when binding a device to VFIO, the UID/GID for the device will
always stay as system default (`root`). Yet, when running DPDK as non-root
user, one has to change the UID/GID of the device to match the user's
UID/GID to use the device.
This patch adds an option to `dpdk-devbind.py` to change the UID/GID of
the device when binding it to VFIO.
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
Notes:
v2 -> v3:
- Replaced error printout back to hard exit
- Reworked UID/GID validation to be at command line parsing
- Simplified chown code
v1 -> v2:
- Replaced hard exit with an error printout
usertools/dpdk-devbind.py | 41 ++++++++++++++++++++++++++++++++++++---
1 file changed, 38 insertions(+), 3 deletions(-)
diff --git a/usertools/dpdk-devbind.py b/usertools/dpdk-devbind.py
index f2a2a9a12f..ed1ef0cabc 100755
--- a/usertools/dpdk-devbind.py
+++ b/usertools/dpdk-devbind.py
@@ -3,11 +3,13 @@
# Copyright(c) 2010-2014 Intel Corporation
#
-import sys
-import os
-import subprocess
import argparse
+import grp
+import os
import platform
+import pwd
+import subprocess
+import sys
from glob import glob
from os.path import exists, basename
@@ -108,6 +110,8 @@
status_flag = False
force_flag = False
noiommu_flag = False
+vfio_uid = -1
+vfio_gid = -1
args = []
@@ -544,6 +548,19 @@ def bind_all(dev_list, driver, force=False):
for d in dev_list:
bind_one(d, driver, force)
+ # if we're binding to vfio-pci, set the IOMMU user/group ownership if one was specified
+ if driver == "vfio-pci" and (vfio_uid != -1 or vfio_gid != -1):
+ # find IOMMU group for a particular PCI device
+ iommu_grp_base_path = os.path.join("/sys/bus/pci/devices", d, "iommu_group")
+ # extract the IOMMU group number
+ iommu_grp = os.path.basename(os.readlink(iommu_grp_base_path))
+ # find VFIO device correspondiong to this IOMMU group
+ dev_path = os.path.join("/dev/vfio", iommu_grp)
+ # set ownership
+ try:
+ os.chown(dev_path, vfio_uid, vfio_gid)
+ except OSError as err:
+ sys.exit(f"Error: failed to set IOMMU group ownership for {d}: {err}")
# For kernels < 3.15 when binding devices to a generic driver
# (i.e. one that doesn't have a PCI ID table) using new_id, some devices
@@ -697,6 +714,8 @@ def parse_args():
global force_flag
global noiommu_flag
global args
+ global vfio_uid
+ global vfio_gid
parser = argparse.ArgumentParser(
description='Utility to bind and unbind devices from Linux kernel',
@@ -746,6 +765,20 @@ def parse_args():
'--noiommu-mode',
action='store_true',
help="If IOMMU is not available, enable no IOMMU mode for VFIO drivers")
+ parser.add_argument(
+ "-U",
+ "--uid",
+ help="For VFIO, specify the UID to set IOMMU group ownership",
+ type=lambda u: pwd.getpwnam(u).pw_uid,
+ default=-1,
+ )
+ parser.add_argument(
+ "-G",
+ "--gid",
+ help="For VFIO, specify the GID to set IOMMU group ownership",
+ type=lambda g: grp.getgrnam(g).gr_gid,
+ default=-1,
+ )
parser.add_argument(
'--force',
action='store_true',
@@ -778,6 +811,8 @@ def parse_args():
b_flag = opt.bind
elif opt.unbind:
b_flag = "none"
+ vfio_uid = opt.uid
+ vfio_gid = opt.gid
args = opt.devices
if not b_flag and not status_flag:
--
2.43.5
prev parent reply other threads:[~2024-11-27 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 13:57 [PATCH v1 " Anatoly Burakov
2024-09-03 9:11 ` Burakov, Anatoly
2024-11-26 15:02 ` [PATCH v2 " Anatoly Burakov
2024-11-26 15:24 ` Bruce Richardson
2024-11-26 16:15 ` Robin Jarry
2024-11-27 8:59 ` Burakov, Anatoly
2024-11-27 9:13 ` Anatoly Burakov [this message]
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=251f3e1bf71c3e873427708d566f677ecd50615c.1732698829.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=rjarry@redhat.com \
/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).