On Thu, Nov 19, 2020 at 11:32:32AM +0000, Anatoly Burakov wrote: > There are common problems with VFIO that get asked over and over on the > mailing list. Document common problems with VFIO and how to fix them or > at least figure out what went wrong. > > Signed-off-by: Anatoly Burakov <anatoly.bura...@intel.com> > ---
One typo spotted below. Acked-by: Bruce Richardson <bruce.richard...@intel.com> > doc/guides/linux_gsg/linux_drivers.rst | 43 ++++++++++++++++++++++++++ > 1 file changed, 43 insertions(+) > > diff --git a/doc/guides/linux_gsg/linux_drivers.rst > b/doc/guides/linux_gsg/linux_drivers.rst > index 9c61850dbb..f3c06c68d1 100644 > --- a/doc/guides/linux_gsg/linux_drivers.rst > +++ b/doc/guides/linux_gsg/linux_drivers.rst > @@ -276,3 +276,46 @@ To restore device ``82:00.0`` to its original kernel > binding: > .. code-block:: console > > ./usertools/dpdk-devbind.py --bind=ixgbe 82:00.0 > + > +Troubleshooting VFIO > +-------------------- > + > +In certain situations, using ``dpdk-devbind.py`` script to bing a device to > VFIO typo: s/bing/bind/
