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 698D2A04C5; Fri, 15 Nov 2019 08:02:08 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 3E519374E; Fri, 15 Nov 2019 08:02:08 +0100 (CET) Received: from mail-il1-f193.google.com (mail-il1-f193.google.com [209.85.166.193]) by dpdk.org (Postfix) with ESMTP id EF8AC374C for ; Fri, 15 Nov 2019 08:02:05 +0100 (CET) Received: by mail-il1-f193.google.com with SMTP id m5so8297736ilq.0 for ; Thu, 14 Nov 2019 23:02:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nsCLEiyY0hmoNsPIIAAX9gXzYBvefZKQ/XknHXaiZ4Y=; b=WqNdJpFIU457wir3L0o8j9fVPUuafQs98Y4rianKiTmy91wBIjQlUEnpDIRLbSQoDV sPPoo4iLrr/oDQXcllUofiQ5FMzgzO07JVB9n5tLcjk8iCFTi+cUTRyAOf4NphvdB8nC koxiKV0swG58K39nXEdZL7Z+LsN98ZboIiSC7twbFK1ySxt3uzKGzzABSTkBrVgAkqMT nSWOMGCdaEEWz55L5nCCspUsvrYtlQIY6AmTHpQa4VQgIn8LRUV+Ly1hzmwdfXxzI5k8 2qb5BfB8FkUUr3ZXH4ZmAiZpoaBfq6p7PcVTglcIMqCfkkCbwdAVhViUQvi6R/4ESLJP VicQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nsCLEiyY0hmoNsPIIAAX9gXzYBvefZKQ/XknHXaiZ4Y=; b=ib/SidsXPkMSOM/dT07cPgs4BoIBVhOczQ8JVfzxCnR/9xF9tj34P1CtKknNkHV3W7 1DJuQt9kecbTqeF5cDBIbNQW8gZxDNmIEhX0h6fY2f14aLdV3MTY9kn50wno3xmD7Ois tPfJsRX1Vhkr513OUZGdIt1EhwAxNzv8fF7M4A4dSTEmZlYWbedjsJnUgGvohtTeGfEW 12UDgPmIj0HNsLhw5wxhbUB2c4cEHVjW/KtEABIrBZDKDWFtjc6YdRqi8HchRwR1YWUt sCrvtANHjMIQTEW0DWw9R+jFUfJyujFT5Za28V8Opi3lWN0cblvOszUlrie3moNJxeyZ OtOA== X-Gm-Message-State: APjAAAXtMtxGAlDOOgpLL5NKhjKRT9dDRu+jgCkgf04A6XP8sSCnNI0q 3t18PS7DvlElCvNxZUiXgonVl5ML/ZvJ36KJXr0= X-Google-Smtp-Source: APXvYqxbLVgm1DtWL1farq+o9dydXvVDC9EhCAZwRH26jqAGSUWStg9Z/6pIx3qDuUKTmEU9d+N1ZHXW34F9ZqUafZo= X-Received: by 2002:a92:aa48:: with SMTP id j69mr14425504ili.162.1573801325173; Thu, 14 Nov 2019 23:02:05 -0800 (PST) MIME-Version: 1.0 References: <20190906091230.13923-1-vattunuru@marvell.com> <20191106153250.77e63a38@x1.home> <41416715.hLTJl77tqX@xps> In-Reply-To: <41416715.hLTJl77tqX@xps> From: Jerin Jacob Date: Fri, 15 Nov 2019 12:31:48 +0530 Message-ID: To: Thomas Monjalon Cc: dpdk-dev , 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 Content-Type: text/plain; charset="UTF-8" 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" On Fri, Nov 15, 2019 at 12:27 PM Thomas Monjalon wrote: > > 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. +1 > >