numam-dpdk/drivers/net/netvsc
Stephen Hemminger f2b76d22f8 net/netvsc: fix probe when VF not found
It is possible that the VF device exists but DPDK doesn't know
about it. This could happen if device was blacklisted or more
likely the necessary device (Mellanox) was not part of the DPDK
configuration.

In either case, the right thing to do is just keep working
but only with the slower para-virtual device.

Fixes: dc7680e859 ("net/netvsc: support integrated VF")
Cc: stable@dpdk.org

Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
2018-12-21 16:22:40 +01:00
..
hn_ethdev.c net/netvsc: fix probe when VF not found 2018-12-21 16:22:40 +01:00
hn_logs.h net/netvsc: add Hyper-V network device 2018-07-13 23:48:07 +02:00
hn_nvs.c net/netvsc: enable SR-IOV 2018-12-19 03:02:08 +01:00
hn_nvs.h net/netvsc: support integrated VF 2018-09-14 20:08:41 +02:00
hn_rndis.c net/netvsc: support integrated VF 2018-09-14 20:08:41 +02:00
hn_rndis.h net/netvsc: support integrated VF 2018-09-14 20:08:41 +02:00
hn_rxtx.c net/netvsc: fix transmit descriptor pool cleanup 2018-12-21 16:22:40 +01:00
hn_var.h net/netvsc: fix transmit descriptor pool cleanup 2018-12-21 16:22:40 +01:00
hn_vf.c net/netvsc: fix VF link update 2018-11-05 20:10:54 +01:00
Makefile net/netvsc: support integrated VF 2018-09-14 20:08:41 +02:00
meson.build net/netvsc: support integrated VF 2018-09-14 20:08:41 +02:00
ndis.h net/netvsc: add Hyper-V network device 2018-07-13 23:48:07 +02:00
rndis.h net/netvsc: add Hyper-V network device 2018-07-13 23:48:07 +02:00
rte_pmd_netvsc_version.map net/netvsc: add Hyper-V network device 2018-07-13 23:48:07 +02:00