DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Robin Jarry <rjarry@redhat.com>
Subject: Re: [PATCH v3 1/1] usertools/devbind: allow changing UID/GID for VFIO
Date: Fri, 29 Nov 2024 14:42:54 +0100	[thread overview]
Message-ID: <3518999.QJadu78ljV@thomas> (raw)
In-Reply-To: <251f3e1bf71c3e873427708d566f677ecd50615c.1732698829.git.anatoly.burakov@intel.com>

27/11/2024 10:13, Anatoly Burakov:
> 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 ++++++++++++++++++++++++++++++++++++---

Please could you update the documentation?
	doc/guides/tools/devbind.rst




      parent reply	other threads:[~2024-11-29 13:43 UTC|newest]

Thread overview: 9+ 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 ` [PATCH v3 " Anatoly Burakov
2024-11-29  8:08   ` Robin Jarry
2024-11-29 13:42   ` Thomas Monjalon [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=3518999.QJadu78ljV@thomas \
    --to=thomas@monjalon.net \
    --cc=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).