There are two warnings in the VFIO section about limitations of VFIO and
limitations on who can bind/unbind devices. Since these don't actually
describe any unsafe conditions, and are more informational, we can
change these to notes. This also helps emphasise the other warnings in
the documents which flag genuine security concerns.
Cc: sta...@dpdk.org
Signed-off-by: Bruce Richardson <bruce.richard...@intel.com>
---
doc/guides/linux_gsg/linux_drivers.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/linux_gsg/linux_drivers.rst
b/doc/guides/linux_gsg/linux_drivers.rst
index 8320db44d9..2e4c80ebd3 100644
--- a/doc/guides/linux_gsg/linux_drivers.rst
+++ b/doc/guides/linux_gsg/linux_drivers.rst
@@ -48,7 +48,7 @@ by calling the script with the ``--help`` or ``--usage``
options.
Note that the UIO or VFIO kernel modules to be used,
should be loaded into the kernel before running the ``dpdk-devbind.py`` script.
-.. warning::
+.. note::
Due to the way VFIO works, there are certain limitations
to which devices can be used with VFIO.
@@ -62,7 +62,7 @@ should be loaded into the kernel before running the
``dpdk-devbind.py`` script.
Therefore, the bridge driver should also be unbound from the bridge PCI
device
for VFIO to work with devices behind the bridge.
-.. warning::
+.. note::
While any user can run the ``dpdk-devbind.py`` script
to view the status of the network ports,
--
2.32.0
