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 EC36FA0598; Sat, 18 Apr 2020 19:37:41 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D452A1D568; Sat, 18 Apr 2020 19:37:41 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 02AE71D561 for ; Sat, 18 Apr 2020 19:37:40 +0200 (CEST) IronPort-SDR: dKwaF8fs+olnx4vHsmM5Nc3PNwJ/hHmXrA29YXMF+i+TZbKmlOHDEDL948ePbfNEXJsjC1oY1a 4aUykbn9fwzA== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Apr 2020 10:37:40 -0700 IronPort-SDR: NwkQM1lO1iExuOVxeBqCuuRr/RUlQHz/8Sdd1v0PbM2LT99joJQLRnNx1/1piLs+Xa8cPifr3E 2Cm4d7vDOOmQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.72,399,1580803200"; d="scan'208";a="257906980" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by orsmga006.jf.intel.com with ESMTP; 18 Apr 2020 10:37:40 -0700 Received: from shsmsx604.ccr.corp.intel.com (10.109.6.214) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.439.0; Sat, 18 Apr 2020 10:37:39 -0700 Received: from shsmsx603.ccr.corp.intel.com (10.109.6.143) by SHSMSX604.ccr.corp.intel.com (10.109.6.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Sun, 19 Apr 2020 01:37:37 +0800 Received: from shsmsx603.ccr.corp.intel.com ([10.109.6.143]) by SHSMSX603.ccr.corp.intel.com ([10.109.6.143]) with mapi id 15.01.1713.004; Sun, 19 Apr 2020 01:37:37 +0800 From: "Wang, Haiyue" To: Thomas Monjalon , "alex.williamson@redhat.com" , "david.marchand@redhat.com" CC: "dev@dpdk.org" , "Burakov, Anatoly" , "vattunuru@marvell.com" , "jerinj@marvell.com" Thread-Topic: [PATCH v7 2/2] eal: support for VFIO-PCI VF token Thread-Index: AQHWFXOqHCf4wskufU2P8jOkgmoeX6h+WQaAgADMDKA= Date: Sat, 18 Apr 2020 17:37:37 +0000 Message-ID: <532deb69643d417e9bdf007d7d746745@intel.com> References: <20200305043311.17065-1-vattunuru@marvell.com> <20200418111642.78874-1-haiyue.wang@intel.com> <20200418111642.78874-3-haiyue.wang@intel.com> <12851687.OFSEd18e0E@thomas> In-Reply-To: <12851687.OFSEd18e0E@thomas> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-reaction: no-action dlp-version: 11.2.0.6 x-originating-ip: [10.239.127.36] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v7 2/2] eal: support for VFIO-PCI VF token 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" > -----Original Message----- > From: Thomas Monjalon > Sent: Saturday, April 18, 2020 21:27 > To: alex.williamson@redhat.com; david.marchand@redhat.com; Wang, Haiyue <= haiyue.wang@intel.com> > Cc: dev@dpdk.org; Burakov, Anatoly ; vattunuru= @marvell.com; > jerinj@marvell.com > Subject: Re: [PATCH v7 2/2] eal: support for VFIO-PCI VF token >=20 > 18/04/2020 13:16, Haiyue Wang: > > --- a/doc/guides/linux_gsg/linux_drivers.rst > > +++ b/doc/guides/linux_gsg/linux_drivers.rst > > +The Linux kernel since version 5.7 supports the creation of virtual fu= nctions, and by default this > feature is off. >=20 > Creation of virtual function has always been supported. > You need to be more specific about the new use case please. >=20 > > +After enabled, the PF needs the VF token in UUID format to setup the t= rust or collaboration between > SR-IOV PF and VFs. > > +The VFs created are bound to vfio-pci module automatically, and the VF= also needs VF token to gain > access to the device. > > +DPDK will use the keyword ``vf_token`` as device argument to pass the = VF token value to PF and its > related VFs. >=20 > You need to explain where the token comes from. Can it be any random UUID= ? >=20 Try to add more in v8, please review.