21/01/2019 11:29, Stojaczyk, Dariusz:
> > It is only possible to know IOMMU type of a given VFIO container
> > by attempting to initialize it. Since secondary process never
> > attempts to set up VFIO container itself (because they're shared
> > between primary and secondary), it never knows which IOMMU type
> > the container is using, and never sets up the appropriate config
> > structures. This results in inability to perform DMA mappings in
> > secondary process.
> >
> > Fix this by allowing secondary process to query IOMMU type of
> > primary's default container at device initialization.
> >
> > Note that this fix is assuming we're only interested in default
> > container.
> >
> > Bugzilla ID: 174
> >
> > Fixes: 6bcb7c95fe14 ("vfio: share default container in multi-process")
> > Cc: dariusz.stojac...@intel.com
> > Cc: sta...@dpdk.org
> >
> > Signed-off-by: Anatoly Burakov <anatoly.bura...@intel.com>
> > ---
>
> Reviewed-by: Darek Stojaczyk <dariusz.stojac...@intel.com>
>
> Thanks!
> In commit 6bcb7c95fe1 (vfio: share default container in multi-process) we
> fixed just the container fd and not the rte_vfio mapping APIs because we did
> not even use those APIs in SPDK.
Applied, thanks
