Hello David and Stephen,
Thanks for your inputs.
As suggested , I compiled testpmd after removing the change below.
+if dpdk_conf.has('RTE_NET_NETVSC')
> +    deps += 'net_netvsc'
> +endif
I ran testpmd with -d option and EAL logging enabled and confirmed that netvsc driver's .so file is being picked by EAL. 

@Stephen Hemminger I also enabled VMBUS logs as per your suggestion and saw that vmbus drivers were being probed.
vmbus_probe_one_driver(): VMBUS device 000d3a42-f83c-000d-3a42-f83c000d3a42 on NUMA socket -1
vmbus_probe_one_driver():   probe driver: net_netvsc
hn_vf_attach(): found matching VF port 0
vmbus_probe_one_driver(): VMBUS device 000d3a42-fbcd-000d-3a42-fbcd000d3a42 on NUMA socket -1
vmbus_probe_one_driver():   probe driver: net_netvsc
hn_vf_attach(): found matching VF port 1

Regards,
Nandini


On Wed, Jun 12, 2024 at 7:48 AM Stephen Hemminger <stephen@networkplumber.org> wrote:
On Fri, 7 Jun 2024 16:31:51 -0700
Nandini Rangaswamy <nandini.rangaswamy@broadcom.com> wrote:

> Hi David,
> Thanks for your email. I inspected meson build output and do see that
> netvsc is in the list of enabled drivers.
> ===============
> Drivers Enabled
> ===============
>
> common:
>         iavf, mlx5, qat,
> bus:
>         auxiliary, pci, vdev, vmbus,
> mempool:
>         bucket, ring, stack,
> dma:
>
> net:
>         af_packet, bond, e1000, ena, failsafe, gve, i40e, iavf,
>         ice, igc, ixgbe, kni, mlx5, *netvsc*, ring, tap,
>         vdev_netvsc, vhost, virtio, vmxnet3,
>
> Also, i changed the meson.build default_library=shared from static and it
> worked.
> Regards,
> Nandini
>
> On Fri, Jun 7, 2024 at 3:56 AM David Marchand <david.marchand@redhat.com>
> wrote:
>
> > Hello,
> >
> > On Thu, Jun 6, 2024 at 11:32 PM Nandini Rangaswamy
> > <nandini.rangaswamy@broadcom.com> wrote: 
> > > I tried compiling the testpmd with DPDK netvsc for openwrt by setting 
> > CONFIG_RTE_LIBRTE_NETVSC_PMD=y . 
> > >
> > > However, when I check ldd testpmd, it does not show any of the dpdk 
> > shared libraries including net_netvsc linked to testpmd binary. 

Testpmd is a special case. It always is statically linked because it has to
have several drivers private API's.  So using ldd to check is not going to give
the right answer.

What is the startup of testpmd look like? You may need to enable debugging of
vmbus and netvsc to see all the reasons the driver decided not to be probed.

This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.