From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Nicolas Pernas Maradei <nico-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: White listing a virtual device
Date: Fri, 07 Nov 2014 15:57:50 +0100 [thread overview]
Message-ID: <1697795.zFSsGeXbRQ@xps13> (raw)
In-Reply-To: <545CD710.4040406-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
2014-11-07 14:28, Nicolas Pernas Maradei:
> 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.
OK, now I better understand your need.
I think that your use case was simply forgotten when designing the
new behaviour.
Could you prepare a patch for this need?
Or maybe you could workaround with a script based on lspci to blacklist all
network devices?
--
Thomas
next prev parent reply other threads:[~2014-11-07 14:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 12:36 White listing a virtual device Nicolas Pernas Maradei
[not found] ` <545CBCE0.2030806-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
2014-11-07 12:55 ` Thomas Monjalon
2014-11-07 13:13 ` Nicolas Pernas Maradei
[not found] ` <545CC581.40309-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
2014-11-07 13:26 ` Neil Horman
[not found] ` <20141107132618.GD25469-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-11-07 13:39 ` Nicolas Pernas Maradei
[not found] ` <545CCBA8.7030900-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
2014-11-07 13:59 ` Thomas Monjalon
2014-11-07 14:02 ` Neil Horman
[not found] ` <20141107140201.GE25469-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2014-11-07 14:28 ` Nicolas Pernas Maradei
[not found] ` <545CD710.4040406-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
2014-11-07 14:57 ` Thomas Monjalon [this message]
2014-11-07 15:01 ` Nicolas Pernas Maradei
2014-11-10 8:13 ` Olivier MATZ
[not found] ` <546073A3.1000008-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
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=1697795.zFSsGeXbRQ@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=nico-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.