From: Stephen Hemminger <stephen@networkplumber.org>
To: Fidaullah Noonari <fidaullah.noonari@emumba.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3] usertools: add check for IOMMU support in dpdk-devbind
Date: Thu, 6 Jul 2023 11:22:45 -0700 [thread overview]
Message-ID: <20230706112245.77fb253d@hermes.local> (raw)
In-Reply-To: <20220321122727.614290-1-fidaullah.noonari@emumba.com>
On Mon, 21 Mar 2022 17:27:27 +0500
Fidaullah Noonari <fidaullah.noonari@emumba.com> wrote:
> binding with vfio driver, when IOMMU is disabled, causes program to crash.
> this patch adds a flag for noiommmu-mode. when this is set, if IOMMU is
> disabled, it changes vfio into unsafe noiommu mode and prints warning
> message.
>
> Signed-off-by: Fidaullah Noonari <fidaullah.noonari@emumba.com>
> ---
Minor indentation issues reported by flake8 python checker:
./usertools/dpdk-devbind.py:489:27: E231 missing whitespace after ','
./usertools/dpdk-devbind.py:494:17: E128 continuation line under-indented for visual indent
./usertools/dpdk-devbind.py:507:17: E128 continuation line under-indented for visual indent
next prev parent reply other threads:[~2023-07-06 18:22 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
2023-07-06 18:22 ` Stephen Hemminger [this message]
2023-10-31 18:34 ` [PATCH v3] usertools: add check for IOMMU support in dpdk-devbind 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=20230706112245.77fb253d@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=fidaullah.noonari@emumba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.