From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) by dpdk.org (Postfix) with ESMTP id 9D3D4590B for ; Fri, 7 Nov 2014 13:46:27 +0100 (CET) Received: by mail-wi0-f181.google.com with SMTP id n3so4482147wiv.8 for ; Fri, 07 Nov 2014 04:55:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=Z16Z7VFMpH1bfeSbjc0x0AwGO8a/s6sFrodR5/mTvWM=; b=nNvZ2CIeMYorktxAJrzJNXR2g6knXPI12m5MgZPVPDWrksf5ud78m/tk9SnwIn9ElC p9tg605S0fJjIwSh+BlbrW2eH5aBOKld71hhIyiVrN0BToBhrJ0TOXNvQAWNNtGQgiKD MizOGrDbRarjgu9Sa/4X3xbBKj1/QKauKKu4ylJG+4yPJ5R/ScDy7OuW9174pi3sxULU FWN6wYN+IHM4Hh5aFiqoJ4xQiHmIcU35Zyw56CJ2ER0dV2eVyclDhVsmbTQy5LjjKDxQ KYIcVv21J1+/v4jS6cqi//dxa/enYCSn2tRQQbidV8vQaeWDW4ssgYC1p6QuYyAT5ZXd igxw== X-Gm-Message-State: ALoCoQkwjoxQoBP0n4yHmLjJkRVFxdqJE5/FjYCmz6t9vOqZdLFHNiZlqd/tqGz3dMGH3omKIwfa X-Received: by 10.180.221.129 with SMTP id qe1mr4877360wic.21.1415364959468; Fri, 07 Nov 2014 04:55:59 -0800 (PST) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id hu3sm11715254wjb.17.2014.11.07.04.55.58 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Nov 2014 04:55:58 -0800 (PST) From: Thomas Monjalon To: Nicolas Pernas Maradei Date: Fri, 07 Nov 2014 13:55:40 +0100 Message-ID: <2085190.a5sr9ou3P7@xps13> Organization: 6WIND User-Agent: KMail/4.14.2 (Linux/3.17.2-1-ARCH; KDE/4.14.2; x86_64; ; ) In-Reply-To: <545CBCE0.2030806@emutex.com> References: <545CBCE0.2030806@emutex.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] White listing a virtual device X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2014 12:46:28 -0000 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