From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Subject: [PATCH v1 1/1] usertools/devbind: add documentation for no-IOMMU mode
Date: Mon, 2 Dec 2024 09:35:01 +0000 [thread overview]
Message-ID: <a1a8fce7e0eb311e7ca673867862a549270f5450.1733132101.git.anatoly.burakov@intel.com> (raw)
Support for `--noiommu-mode` flag was added, but documentation for it was
not. Add documentation for the flag.
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
---
doc/guides/tools/devbind.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/doc/guides/tools/devbind.rst b/doc/guides/tools/devbind.rst
index 841615570f..e010d4b7df 100644
--- a/doc/guides/tools/devbind.rst
+++ b/doc/guides/tools/devbind.rst
@@ -62,6 +62,11 @@ OPTIONS
Use this flag to change ownership to the specified user and group, so that
devices bound to VFIO would be usable by unprivileged users.
+* ``--noiommu-mode``
+
+ When using vfio-pci driver on a system with no IOMMU, this flag should be used to
+ enable unsafe no-IOMMU mode for vfio-pci driver.
+
.. warning::
--
2.43.5
next reply other threads:[~2024-12-02 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 9:35 Anatoly Burakov [this message]
2024-12-04 12:33 ` Burakov, Anatoly
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=a1a8fce7e0eb311e7ca673867862a549270f5450.1733132101.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--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).