From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerinjacobk@gmail.com>
Cc: dev@dpdk.org, Alex Williamson <alex.williamson@redhat.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Vamsi Krishna Attunuru <vattunuru@marvell.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
maxime.coquelin@redhat.com,
Stephen Hemminger <stephen@networkplumber.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
David Marchand <david.marchand@redhat.com>,
Luca Boccassi <bluca@debian.org>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Kevin Traynor <ktraynor@redhat.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
Liang-Min Wang <liang-min.wang@intel.com>,
Alexander Duyck <alexander.h.duyck@intel.com>,
Peter Xu <peterx@redhat.com>, Eric Auger <eric.auger@redhat.com>
Subject: Re: [dpdk-dev] [PATCH v1 1/1] kernel/linux: introduce vfio_pf kernel module
Date: Fri, 15 Nov 2019 07:57:24 +0100 [thread overview]
Message-ID: <41416715.hLTJl77tqX@xps> (raw)
In-Reply-To: <CALBAE1OR7FH2mWqdqgSguTkdbs94x+22PO+yLiKdb=+pncv0Zg@mail.gmail.com>
07/11/2019 06:02, Jerin Jacob:
> On Thu, Nov 7, 2019 at 4:03 AM Alex Williamson
> <alex.williamson@redhat.com> wrote:
> > Ideas have been suggested
> > upstream for for quarantining VFs generated from user owned PFs such
> > that we require an opt-in to make use of them in this way. Nobody
> > seems to be pursuing such ideas upstream. I don't even see upstream
> > proposals to add a scary sounding module option to vfio-pci that would
> > taint the kernel, but make this available. If nothing else, please
> > remove the vfio name from this abomination, it has nothing to do with
> > vfio other than to try to subvert the security and isolation that vfio
> > attempts to provide.
>
> Thanks for the feedback. Let's hold on accepting this patch.
>
> We would like to have an upstream solution so that DPDK needs to only focus
> on userspace.
>
> I will work on submitting a patch for the discussion in Linux upstream.
> Let see how the discussion goes, Based on the that, We can revisit
> fate of this module.
Just to be clear, vfio_pf is on hold, i.e. not merged in DPDK 19.11.
next prev parent reply other threads:[~2019-11-15 6:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 9:12 vattunuru
2019-09-06 9:45 ` Thomas Monjalon
2019-09-06 13:27 ` Jerin Jacob Kollanukkaran
2019-09-25 4:06 ` Vamsi Krishna Attunuru
2019-09-25 7:18 ` Andrew Rybchenko
2019-10-08 5:07 ` Vamsi Krishna Attunuru
2019-10-31 17:03 ` Thomas Monjalon
2019-11-01 11:54 ` Luca Boccassi
2019-11-01 12:12 ` Jerin Jacob
2019-11-04 11:16 ` Bruce Richardson
2019-11-05 10:09 ` Luca Boccassi
2019-11-06 22:32 ` Alex Williamson
2019-11-07 5:02 ` Jerin Jacob
2019-11-15 6:57 ` Thomas Monjalon [this message]
2019-11-15 7:01 ` Jerin Jacob
2019-10-08 15:12 ` Stephen Hemminger
2019-10-08 15:28 ` Jerin Jacob
2019-10-09 23:28 ` Stephen Hemminger
2019-10-10 6:02 ` Jerin Jacob
2019-10-13 7:20 ` Jerin Jacob
2019-10-16 11:37 ` Jerin Jacob
2019-10-23 17:08 ` Jerin Jacob
2019-10-24 11:08 ` Jerin Jacob
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=41416715.hLTJl77tqX@xps \
--to=thomas@monjalon.net \
--cc=alex.williamson@redhat.com \
--cc=alexander.h.duyck@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=arybchenko@solarflare.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=eric.auger@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktraynor@redhat.com \
--cc=liang-min.wang@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=peterx@redhat.com \
--cc=stephen@networkplumber.org \
--cc=vattunuru@marvell.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).