Re: [dpdk-dev] White listing a virtual device

[Neil Horman <nhorman@tuxdriver.com>]

On Fri, Nov 07, 2014 at 01:39:52PM +0000, Nicolas Pernas Maradei wrote:
> 
> On 07/11/14 13:26, Neil Horman wrote:
> >Then you create the pcap device with --vdev, and simply don't load the pmds for
> >any of your physical devices (or just don't use pci-whitelist at all if you're
> >doing a static build).  If you do that, then the corresponding niantic driver
> >won't initialize any of the hardware, you'll only get the pcap port.
> >
> >Neil
> 
> Hi Neil,
> 
> What you are saying is just another way to black list the ports I don't want
> to use. I'm aware of that option (as well as using the -b option) but in our
> particular case we have several systems under test with different
> configurations and we want to use this virtual port only. Which seems to be
> a perfect use case for white listing rather than black listing or modifying
> the system configuration.
> 
> As far as I remember this option was available in previous versions.
> 
> Thanks,
> Nico.
> 

Ah, you want the -w option then, it still appears in the short options list in
my tree. That sets up the option parsing for all pci devices to require
whitelisting to be initalized.  virtual devices are exempt from this process
because declaring them with --vdev implicitly means you want to use them.

Neil