From: Anatoly Burakov <anatoly.burakov@intel.com> To: dev@dpdk.org Cc: thomas@monjalon.net Subject: [dpdk-dev] [PATCH 3/4] doc: add VFIO no-IOMMU Linux GSG section Date: Tue, 10 Nov 2020 18:09:49 +0000 Message-ID: <35caad93521712ef3dfe1f79fe4acd765f4cad07.1605031542.git.anatoly.burakov@intel.com> (raw) In-Reply-To: <7d1840b4184bf363e3b9ddaff0683f13b324078a.1605031542.git.anatoly.burakov@intel.com> In-Reply-To: <7d1840b4184bf363e3b9ddaff0683f13b324078a.1605031542.git.anatoly.burakov@intel.com> Currently, we have no documentation on how to use VFIO in no-IOMMU mode. Add such documentation. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> --- doc/guides/linux_gsg/linux_drivers.rst | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/doc/guides/linux_gsg/linux_drivers.rst b/doc/guides/linux_gsg/linux_drivers.rst index 34fd2f8652..4148602a63 100644 --- a/doc/guides/linux_gsg/linux_drivers.rst +++ b/doc/guides/linux_gsg/linux_drivers.rst @@ -75,9 +75,30 @@ To make use of full VFIO functionality, both kernel and BIOS must support and be For proper operation of VFIO when running DPDK applications as a non-privileged user, correct permissions should also be set up. This can be done by using the DPDK setup script (called ``dpdk-setup.sh`` and located in the usertools directory). +VFIO no-IOMMU mode +------------------ + +If there is no IOMMU available on the system, VFIO can still be used, but it has +to be loaded with an additional module parameter: + +.. code-block:: console + + # modprobe vfio enable_unsafe_noiomu_mode=1 + +Alternatively, one can also enable this option in an already loaded kernel module: + +.. code-block:: console + + # echo 1 > /sys/module/vfio/parameters/enable_unsafe_noiomu_mode + +After that, VFIO can be used with hardware devices as usual. + .. note:: - VFIO can be used without IOMMU. While this is unsafe, it does make it possible for the user to keep the degree of device access and programming that VFIO has, in situations where IOMMU is not available. + Since no-IOMMU mode forgoes IOMMU protection, it is inherently unsafe. That + said, it does make it possible for the user to keep the degree of device + access and programming that VFIO has, in situations where IOMMU is not + available. UIO --- -- 2.17.1
next prev parent reply other threads:[~2020-11-10 18:10 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-10 18:09 [dpdk-dev] [PATCH 1/4] doc: move VFIO driver to be first Anatoly Burakov 2020-11-10 18:09 ` [dpdk-dev] [PATCH 2/4] doc: reword VFIO and UIO Linux GSG section Anatoly Burakov 2020-11-10 18:09 ` Anatoly Burakov [this message] 2020-11-10 18:09 ` [dpdk-dev] [PATCH 4/4] doc: add VFIO troubleshooting section Anatoly Burakov 2020-11-18 15:37 ` [dpdk-dev] [PATCH v2 1/4] doc: move VFIO driver to be first Anatoly Burakov 2020-11-18 18:24 ` David Marchand 2020-11-19 11:04 ` Burakov, Anatoly 2020-11-19 11:32 ` [dpdk-dev] [PATCH v3 " Anatoly Burakov 2020-11-23 17:22 ` Ferruh Yigit 2020-11-19 11:32 ` [dpdk-dev] [PATCH v3 2/4] doc: reword VFIO and UIO Linux GSG section Anatoly Burakov 2020-11-19 11:32 ` [dpdk-dev] [PATCH v3 3/4] doc: add VFIO no-IOMMU " Anatoly Burakov 2020-11-27 15:47 ` Bruce Richardson 2020-11-19 11:32 ` [dpdk-dev] [PATCH v3 4/4] doc: add VFIO troubleshooting section Anatoly Burakov 2020-11-27 15:30 ` Thomas Monjalon 2020-11-27 15:57 ` Burakov, Anatoly 2020-11-27 15:49 ` Bruce Richardson 2020-11-27 16:29 ` Kevin Traynor 2020-11-27 17:27 ` Thomas Monjalon 2020-11-18 15:37 ` [dpdk-dev] [PATCH v2 2/4] doc: reword VFIO and UIO Linux GSG section Anatoly Burakov 2020-11-18 15:37 ` [dpdk-dev] [PATCH v2 3/4] doc: add VFIO no-IOMMU " Anatoly Burakov 2020-11-18 15:37 ` [dpdk-dev] [PATCH v2 4/4] doc: add VFIO troubleshooting section Anatoly Burakov
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=35caad93521712ef3dfe1f79fe4acd765f4cad07.1605031542.git.anatoly.burakov@intel.com \ --to=anatoly.burakov@intel.com \ --cc=dev@dpdk.org \ --cc=thomas@monjalon.net \ /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
DPDK patches and discussions This inbox may be cloned and mirrored by anyone: git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \ dev@dpdk.org public-inbox-index dev Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/public-inbox.git