On Fri, 7 Jun 2024 16:31:51 -0700 Nandini Rangaswamy <nandini.rangasw...@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.march...@redhat.com> > wrote: > > > Hello, > > > > On Thu, Jun 6, 2024 at 11:32 PM Nandini Rangaswamy > > <nandini.rangasw...@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.
