[dpdk-dev] [PATCH] tailq: secondary process may not have all tailq available

[Hemant Agrawal]

On 1/14/2021 7:14 PM, David Marchand wrote:
> On Thu, Jan 14, 2021 at 8:24 AM Hemant Agrawal <hemant.agrawal at nxp.com> wrote:
>> Secondary process may not have all the tailq available for
>> mapping, so better to ignore the error.
>>
>> e.g. if the primary process is linked with N libs
>> and secondary process is linked with less number of libs.
>>
>> dpdk-procinfo results into following error:
>> EAL: Cannot initialize tailq: VMBUS_RESOURCE_LIST
> For dpdk-procinfo to complain about vmbus, it means the bus driver has
> been loaded in the secondary, but not in the primary.
> Is this what you intend to do?
>
Yes.

Typically the customer applications are built/linked with only limited  
number of bus, devices

dpdk-procinfo is getting compiled with default list as part of dpdk 
build. so, if customer is trying to use the default dpdk-procinfo with 
their application - there will be differences.