[dpdk-dev] [PATCH v10 6/9] eal: auto detect iova mode
thomas at monjalon.net
Fri Oct 13 11:58:14 CEST 2017
13/10/2017 10:48, Maxime Coquelin:
> Hi Santosh,
> On 10/06/2017 01:03 PM, Santosh Shukla wrote:
> > iova autodetection depends on rte_bus_scan result. Result of bus scan will
> > have updated device_list and each device in that list has its '.kdev' state
> > updated. That kdrv state used to detect iova mapping mode for that device.
> > _device_parse() has dependency on rt_bus_scan so,
> > Below calls moved up in the eal initialization order:
> > - eal_option_device_parse
> > - rte_bus_scan
> > And based on the result of rte_bus_scan_iommu_class - select iova
> > mapping mode.
> > Signed-off-by: Santosh Shukla <santosh.shukla at caviumnetworks.com>
> > Signed-off-by: Jerin Jacob <jerin.jacob at caviumnetworks.com>
> > Reviewed-by: Maxime Coquelin <maxime.coquelin at redhat.com>
> > Reviewed-by: Anatoly Burakov <anatoly.burakov at intel.com>
> > Tested-by: Hemant Agrawal <hemant.agrawal at nxp.com>
> > ---
> > lib/librte_eal/bsdapp/eal/eal.c | 27 ++++++++++++++++-----------
> > lib/librte_eal/linuxapp/eal/eal.c | 27 ++++++++++++++++-----------
> > 2 files changed, 32 insertions(+), 22 deletions(-)
> We noticed a regression on current master, which prevents to use Vhost
> PMD with CONFIG_RTE_BUILD_SHARED_LIB=y:
It was my guess during review:
I really don't understand how it can work,
because the bus scan is moved before shared libraries (plugins)
It will be even worst when PCI and vdev buses will be some
Is it a chicken/egg issue?
If we cannot find a good solution, we may have to revert for RC1.
More information about the dev