From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: White listing a virtual device Date: Fri, 07 Nov 2014 13:55:40 +0100 Message-ID: <2085190.a5sr9ou3P7@xps13> References: <545CBCE0.2030806@emutex.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Nicolas Pernas Maradei Return-path: In-Reply-To: <545CBCE0.2030806-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" Hi Nicolas, 2014-11-07 12:36, Nicolas Pernas Maradei: > 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. Yes > 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? It's by design. If you add a vdev, you want to use it and there is no reason to whitelist it, and especially no reason to blacklist a device you created for your usage. Do you agree? Is there a part of the documentation which should be improved? -- Thomas