From: Nicolas Pernas Maradei <nico@emutex.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] White listing a virtual device
Date: Fri, 07 Nov 2014 14:28:32 +0000 [thread overview]
Message-ID: <545CD710.4040406@emutex.com> (raw)
In-Reply-To: <20141107140201.GE25469@hmsreliant.think-freely.org>
On 07/11/14 14:02, Neil Horman wrote:
> 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
Hi Neil,
Thanks for your reply. The -w option is the same as --pci-whitelist
mentioned in my first email. Declaring a virtual device with --vdev
means that I want to use it but there doesn't seem to be a way to say
that I want to use only that device. Clearly the white list option is
the way to specify this but if virtual devices are excluded from
-w/--pci-whitelist you can't only white list the virtual devices.
I want to be able to have the same command line arguments across several
systems under test without having to know where the physical devices are
(to black list them).
My issue is not that I don't want to black list the physical devices
it's just that I want to white list the virtual ones. I don't see why
that option is not available.
Thanks,
Nico.
next prev parent reply other threads:[~2014-11-07 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 12:36 Nicolas Pernas Maradei
2014-11-07 12:55 ` Thomas Monjalon
2014-11-07 13:13 ` Nicolas Pernas Maradei
2014-11-07 13:26 ` Neil Horman
2014-11-07 13:39 ` Nicolas Pernas Maradei
2014-11-07 13:59 ` Thomas Monjalon
2014-11-07 14:02 ` Neil Horman
2014-11-07 14:28 ` Nicolas Pernas Maradei [this message]
2014-11-07 14:57 ` Thomas Monjalon
2014-11-07 15:01 ` Nicolas Pernas Maradei
2014-11-10 8:13 ` Olivier MATZ
2014-11-16 21:07 ` Nicolas Pernas Maradei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545CD710.4040406@emutex.com \
--to=nico@emutex.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).