From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>
Subject: [dpdk-dev] [PATCH v2 1/1] doc: clarify VFIO doc for built-in modules
Date: Wed, 27 Oct 2021 15:37:14 +0000 [thread overview]
Message-ID: <f28a1eadad851e69062b60cc2e6a4e0f3eb58c09.1635349028.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <b1e6b0a56a4017be375a1a2471c3fcd574d487e0.1634215954.git.anatoly.burakov@intel.com>
Currently, the documentation only contains instructions for enabling
SRIOV support for VFIO compiled as a module, but doesn't have any
instructions on how to do the same for cases where VFIO is built-in.
Add these instructions.
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
---
doc/guides/linux_gsg/linux_drivers.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/linux_gsg/linux_drivers.rst b/doc/guides/linux_gsg/linux_drivers.rst
index c6b6881ea2..2dd711bb37 100644
--- a/doc/guides/linux_gsg/linux_drivers.rst
+++ b/doc/guides/linux_gsg/linux_drivers.rst
@@ -65,6 +65,12 @@ The token will be used for all PF and VF ports within the application.
sudo modprobe vfio-pci enable_sriov=1
+ Alternatively, pass the ``enable_sriov`` parameter through the ``sysfs`` if the module is already loaded or is built-in:
+
+ .. code-block:: console
+
+ echo 1 | sudo tee /sys/module/vfio_pci/parameters/enable_sriov
+
#. Bind the PCI devices to ``vfio-pci`` driver
.. code-block:: console
--
2.25.1
next prev parent reply other threads:[~2021-10-27 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 12:52 [dpdk-dev] [PATCH v1 1/1] doc: clarify vfio " Anatoly Burakov
2021-10-14 15:12 ` Bruce Richardson
2021-10-14 19:47 ` Iremonger, Bernard
2021-10-27 15:35 ` Burakov, Anatoly
2021-10-27 15:37 ` Anatoly Burakov [this message]
2021-10-28 8:14 ` [dpdk-dev] [PATCH v2 1/1] doc: clarify VFIO " David Marchand
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=f28a1eadad851e69062b60cc2e6a4e0f3eb58c09.1635349028.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@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).