From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3E2ADA04C0; Fri, 15 Nov 2019 07:57:33 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8A46D374E; Fri, 15 Nov 2019 07:57:32 +0100 (CET) Received: from new4-smtp.messagingengine.com (new4-smtp.messagingengine.com [66.111.4.230]) by dpdk.org (Postfix) with ESMTP id A8D1E374C for ; Fri, 15 Nov 2019 07:57:30 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id CCFC65A13; Fri, 15 Nov 2019 01:57:29 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 15 Nov 2019 01:57:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=VjMg3y9yC7c6fuiQl0or0Y/QmIHh3GquzXtHGyI/gxE=; b=UJk+Ixq2g04c 5tn5Vf94yGt/H6YIUjfR7X0y1t4eJr8zQ5fMgMSEbf5+I8mntBxjPoRS2mvRbbw5 Wt1uDDoFLxSG12cFafJ2vaTpdtbUGuIk1Bv2VMIcpcVEaip9/koMP4QzB/wu3+zp wsuAMa4/eGHSUuO+NVSzZVMNr2FyzE0= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=VjMg3y9yC7c6fuiQl0or0Y/QmIHh3GquzXtHGyI/g xE=; b=X7fGLG2cHm2j1TDW6V9BruZuZTgKfTRayk0zJ9v3mwrhJ5iTMG2+3QOb0 u1pbWBy1WOcEv4IADTd33ceqCfzXMuRW+jqQQ4b1I87E/sm5yFBUVVneehtVOjXW wQGApLV+Ym95wOqupIimB3+FoG9+KJvlgHJo94LTSa5yaQ2QDBbgKhgWfO3z4nvw x8HGn/2jeIE7dSch1aeoYKoj02egFf2QdNy1f8h0vQOj3DO7HpmQ6XX8em3+Og1X /W6nMS6lRWU1LpXrvKbT4v3wG1n1THJf3/Ei56f1SxrDvOVxdxa1o4NKnyt1Yd5j ELp6taKowaLUjlE5fwvN7baUKEzSA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudefgedguddtudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc fkphephedtrddvvdehrddujeekrddvfeeknecurfgrrhgrmhepmhgrihhlfhhrohhmpeht hhhomhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (unknown [50.225.178.238]) by mail.messagingengine.com (Postfix) with ESMTPA id 82C6480059; Fri, 15 Nov 2019 01:57:26 -0500 (EST) From: Thomas Monjalon To: Jerin Jacob Cc: dev@dpdk.org, Alex Williamson , Jerin Jacob Kollanukkaran , Vamsi Krishna Attunuru , Andrew Rybchenko , Ferruh Yigit , maxime.coquelin@redhat.com, Stephen Hemminger , "Richardson, Bruce" , David Marchand , Luca Boccassi , Christian Ehrhardt , Kevin Traynor , Anatoly Burakov , "Ananyev, Konstantin" , Honnappa Nagarahalli , Liang-Min Wang , Alexander Duyck , Peter Xu , Eric Auger Date: Fri, 15 Nov 2019 07:57:24 +0100 Message-ID: <41416715.hLTJl77tqX@xps> In-Reply-To: References: <20190906091230.13923-1-vattunuru@marvell.com> <20191106153250.77e63a38@x1.home> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v1 1/1] kernel/linux: introduce vfio_pf kernel module X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 07/11/2019 06:02, Jerin Jacob: > On Thu, Nov 7, 2019 at 4:03 AM Alex Williamson > 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.