From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>,
Fidaullah Noonari <fidaullah.noonari@emumba.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] usertools/devbind: add support for non-IOMMU mode
Date: Thu, 17 Oct 2024 17:34:55 +0200 [thread overview]
Message-ID: <6594279.j6PcuT4dK6@thomas> (raw)
In-Reply-To: <Zv5jjOezKCCcFUUW@bricha3-mobl1.ger.corp.intel.com>
03/10/2024 11:27, Bruce Richardson:
> On Wed, Oct 02, 2024 at 11:13:12AM -0700, Stephen Hemminger wrote:
> > From: Fidaullah Noonari <fidaullah.noonari@emumba.com>
> >
> > 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>
> > ---
> > v2 - rebase patch and fix some minor stuff
> > remove unneeded f.close, simplify error and help messages
> >
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Applied with few wording changes, thanks.
next prev parent reply other threads:[~2024-10-17 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 6:26 [PATCH v2] usertools: add check for IOMMU support in dpdk-devbind Fidaullah Noonari
2022-03-15 9:17 ` Bruce Richardson
2022-03-21 12:27 ` [PATCH v3] " Fidaullah Noonari
2022-03-31 14:37 ` Burakov, Anatoly
2022-03-31 14:44 ` Bruce Richardson
2022-10-10 23:02 ` Thomas Monjalon
2022-10-12 12:38 ` [PATCH v4] " Fidaullah Noonari
2024-07-01 17:51 ` Stephen Hemminger
2024-10-02 18:13 ` [PATCH] usertools/devbind: add support for non-IOMMU mode Stephen Hemminger
2024-10-03 9:27 ` Bruce Richardson
2024-10-17 15:34 ` Thomas Monjalon [this message]
2023-07-06 18:22 ` [PATCH v3] usertools: add check for IOMMU support in dpdk-devbind Stephen Hemminger
2023-10-31 18:34 ` Stephen Hemminger
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=6594279.j6PcuT4dK6@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fidaullah.noonari@emumba.com \
--cc=stephen@networkplumber.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).