From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 25A6F1B2A2 for ; Mon, 30 Oct 2017 08:25:24 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Oct 2017 00:25:23 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,318,1505804400"; d="scan'208,217";a="329467209" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga004.fm.intel.com with ESMTP; 30 Oct 2017 00:25:23 -0700 Received: from fmsmsx111.amr.corp.intel.com (10.18.116.5) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 30 Oct 2017 00:25:23 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by fmsmsx111.amr.corp.intel.com (10.18.116.5) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 30 Oct 2017 00:25:22 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.175]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.218]) with mapi id 14.03.0319.002; Mon, 30 Oct 2017 15:25:20 +0800 From: "Xu, Qian Q" To: "Lin, Xueqin" , "gaetan.rivet@6wind.com" , "Zhang, Helin" , "Thomas Monjalon" CC: "Pei, Yulong" , "Peng, Yuan" , "Xu, Qian Q" , "dev@dpdk.org" , "Glynn, Michael J" , "Liu, Yu Y" Thread-Topic: vfio-pci blocking issue Thread-Index: AdNRTx4UyirD9w82TfOyk30jMmdifw== Date: Mon, 30 Oct 2017 07:25:20 +0000 Message-ID: <82F45D86ADE5454A95A89742C8D1410E3B7F050C@shsmsx102.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNjE2ZDQxZGYtNjg2MC00OTNkLTg0NWEtMWM3Yjg5MDE1MmI4IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6ImdsQWNBMFFHODNiYlBjOWV0UW4ydW1rc24wd3VDbm9zVStacVJvcDBpYzQ9In0= x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] vfio-pci blocking issue 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: , X-List-Received-Date: Mon, 30 Oct 2017 07:25:26 -0000 We have found the blocking issue about vfio-pci in RC2, which blocked many = test cases. It is a blocking issue for 17.11 release. Please help check. Add more failed case as below: it will also cause the VF port can't be prob= ed. ? Components version dpdk 17.11 rc2 ? Defect component version (release version or repo/branch/commit ID) ? Environment components version (QEMU, OVS, etc) ? HW platform info fvl10g ? Test Steps and Test Result 1. Created VFs and bind to vfio-pci ./usertools/dpdk-devbind.py --bind=3Digb_uio 81:00.0 81:00.1 echo 1 > /sys/bus/pci/devices/0000:81:00.0/max_vfs echo 1 > /sys/bus/pci/devices/0000:81:00.1/max_vfs ./usertools/dpdk-devbind.py -s 0000:05:02.0 'XL710/X710 Virtual Function 154c' if=3D drv=3Di40evf unused= =3Digb_uio 0000:05:06.0 'XL710/X710 Virtual Function 154c' if=3D drv=3Di40evf unused= =3Digb_uio ./usertools/dpdk-devbind.py --bind=3Dvfio-pci 81:02.0 81:06.0 ./usertools/dpdk-devbind.py -s 0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=3Digb_uio u= nused=3Dvfio-pci 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=3Digb_uio u= nused=3Dvfio-pci 0000:81:02.0 'XL710/X710 Virtual Function 154c' drv=3Dvfio-pci unused=3Digb= _uio 0000:81:06.0 'XL710/X710 Virtual Function 154c' drv=3Dvfio-pci unused=3Digb= _uio 2. up PF with testpmd, ./x86_64-native-linuxapp-gcc/app/testpmd -l 23-27 -n 4 --socket-mem=3D1024,= 1024 --file-prefix=3Dpf -w 81:00.0 -w 81:00.1 - -i --rxq=3D4 --txq=3D4 3. start VFs with testpmd, ./x86_64-native-linuxapp-gcc/app/testpmd -l 28-32 -n 4 --socket-mem=3D1024,= 1024 --file-prefix=3Dvf -w 81:02.0 -w 81:06.0 - -i --rxq=3D4 --txq=3D4 EAL: Detected 88 lcore(s) EAL: Some devices want iova as va but pa will be used because.. EAL: vfio-n= oiommu mode configured EAL: Probing VFIO support... EAL: VFIO support initialized EAL: PCI device 0000:81:02.0 on NUMA socket 1 EAL: probe driver: 8086:154c net_i40e_vf EAL: Requested device 0000:81:02.0 cannot be used EAL: PCI device 0000:81:06.0 on NUMA socket 1 EAL: probe driver: 8086:154c net_i40e_vf EAL: Requested device 0000:81:06.0 cannot be used EAL: No probed ethernet devices Interactive-mode selected USER1: create a new mbuf pool : n=3D179456, size=3D2176= , socket=3D0 USER1: create a new mbuf pool : n=3D179456, size=3D2176= , socket=3D1 Done testpmd> it can be seen "No probed ethernet devices" From: Lin, Xueqin Sent: Monday, October 30, 2017 1:59 PM To: gaetan.rivet@6wind.com; Zhang, Helin Cc: Xu, Qian Q ; Pei, Yulong ; P= eng, Yuan Subject: vfio-pci Hi Rivet, Some cases need to bind port to vfio-pci, for example, test inline inpsec. 1. modprobe vfio-pci 2. bind port to vfio-pci ./usertools/dpdk-devbind.py -b vfio-pci 81:00.0 81:00.1 3. Run ipsec sudo ./build/ipsec-secgw -l 20,21 -w 81:00.0 -w 81:00.1 --vdev "crypto_nu= ll" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u 0x2 -j 9000\ --config=3D"(0,0,20),(1,0,21)" -f ./enc.cfg Find error as below, vfio-pci can't be used. EAL: probe driver: 8086:10fb net_ixgbe EAL: Requested device 0000:81:00.0 cannot be used EAL: PCI device 0000:81:00.1 on NUMA socket 1 EAL: probe driver: 8086:10fb net_ixgbe EAL: Requested device 0000:81:00.1 cannot be used EAL: Search driver crypto_null to probe device crypto_null CRYPTODEV: [crypto_null] - Creating cryptodev crypto_null Find your patch results in the error, block lots of vfio-pci cases, which i= s urgent. DPDK-4026 should meet s= ame issue. If any wrong to use vfio-pci, could you give a guide? commit 279b581c897d4bf01f2b35c7327e767400c3ee80 Author: Gaetan Rivet = > Date: Thu Oct 26 12:05:52 2017 +0200 vfio: expose functions The following symbols are used by vfio implementations within the PCI b= us. They need to be publicly available for the PCI bus to be outside the EAL. Best regards, Xueqin