From: Ali Alnubani <alialnu@nvidia.com>
To: <dev@dpdk.org>
Subject: [PATCH] doc: update mlxreg command arguments for recent versions
Date: Mon, 3 Jul 2023 10:48:20 +0300 [thread overview]
Message-ID: <20230703074820.502473-1-alialnu@nvidia.com> (raw)
Recent versions of the command require vhca_id and all_vhca
to be set with the --indexes arg.
Signed-off-by: Ali Alnubani <alialnu@nvidia.com>
---
doc/guides/nics/mlx5.rst | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 7a137d5f6a..68ecdbec15 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -1887,9 +1887,15 @@ The procedure below is an example of using a ConnectX-5 adapter card (pf0) with
$ ip link set p0 vf 0 trust on
$ ip link set p0 vf 1 trust on
-#. Configure all VFs using mlxreg::
+#. Configure all VFs using mlxreg:
- $ mlxreg -d /dev/mst/mt4121_pciconf0 --reg_name VHCA_TRUST_LEVEL --yes --set "all_vhca=0x1,trust_level=0x1"
+ - For MFT >= 4.21::
+
+ $ mlxreg -d /dev/mst/mt4121_pciconf0 --reg_name VHCA_TRUST_LEVEL --yes --indexes 'all_vhca=0x1,vhca_id=0x0' --set 'trust_level=0x1'
+
+ - For MFT < 4.21::
+
+ $ mlxreg -d /dev/mst/mt4121_pciconf0 --reg_name VHCA_TRUST_LEVEL --yes --set "all_vhca=0x1,trust_level=0x1"
.. note::
--
2.25.1
next reply other threads:[~2023-07-03 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 7:48 Ali Alnubani [this message]
2023-07-03 14:07 ` Raslan Darawsheh
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=20230703074820.502473-1-alialnu@nvidia.com \
--to=alialnu@nvidia.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).