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 13:55:40 +0100 [thread overview]
Message-ID: <2085190.a5sr9ou3P7@xps13> (raw)
In-Reply-To: <545CBCE0.2030806-M3NBUjLqch7QT0dZR+AlfA@public.gmane.org>
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
next prev parent reply other threads:[~2014-11-07 12:55 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 [this message]
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
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=2085190.a5sr9ou3P7@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 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).