[dpdk-dev] White listing a virtual device

[Nicolas Pernas Maradei <nico@emutex.com>]

Hi,

I'm currently using the --vdev option to create virtual devices, mainly 
for testing. I noticed that these virtual devices are not being 
white-listed any more. That was the original behaviour when the option 
was called --use-device. Instead of that the virtual device is being 
added to the device list along with the real ones.

You can see this behaviour by running testpmd as shown below. I have 4 
Niantics on my system and they are all bound to igb_uio driver. You can 
see the 5 ports being reported.

Now, the --pci-whitelist argument lets you white list a device but it 
only accepts a PCI address as an option. My question is, how do you 
white list a virtual device? Did this feature get dropped when the 
--use-device was split into --vdev and --pci-whitelist back in 
March/April or is this just an unhandled corner case?


     [nico dpdk]((v1.7.1))# sudo 
./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 3 
--vdev=eth_pcap0,rx_pcap=eth_ipv4.pcap,tx_pcap=/dev/null
     ...

     Configuring Port 0 (socket 0)
     Port 0: 00:00:00:01:02:03       <---- PCAP virtual device
     Configuring Port 1 (socket 0)
     Port 1: 90:E2:BA:6D:EC:D4
     Configuring Port 2 (socket 0)
     Port 2: 90:E2:BA:6D:EC:D5
     Configuring Port 3 (socket 0)
     Port 3: 90:E2:BA:74:6C:B4
     Configuring Port 4 (socket 0)
     Port 4: 90:E2:BA:74:6C:B5
     Checking link statuses...
     Port 0 Link Up - speed 10000 Mbps - full-duplex
     Port 1 Link Up - speed 10000 Mbps - full-duplex
     Port 2 Link Up - speed 10000 Mbps - full-duplex
     Port 3 Link Up - speed 10000 Mbps - full-duplex
     Port 4 Link Up - speed 10000 Mbps - full-duplex
     Done
     No commandline core given, start packet forwarding
     ...


Thanks,
Nico.