From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f169.google.com (mail-wr0-f169.google.com [209.85.128.169]) by dpdk.org (Postfix) with ESMTP id DD6BF1B2FB for ; Mon, 30 Oct 2017 09:14:21 +0100 (CET) Received: by mail-wr0-f169.google.com with SMTP id l8so11609972wre.12 for ; Mon, 30 Oct 2017 01:14:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=VM3wn61H1VjiqZ/GdSQDgtkbXd9RLqWAj9a8bCiL1Hc=; b=hF0xM0cZfYaML4lbfa3onxPQeIg9cUsrsm0Us+sCzkUlPibeth15adHn2bsZlC0ml3 xLGeEFK6MreLmVJ31LBNd9NjwKsyoPLSOa/5u0rq2yKNcf621vGnH/LE3oovJy/Bx6zf fh/hsv/LlcWlnqG1kub25+9qvOIVjsFqNAx9ys5SQN8gSWVGnQfpwdMz3fonnNSJmEy6 P8bvsTaIX4uAQMTCc/KynwbekofmjUbhtFKLysTdSOaCmI4pgzHfJOQYN7gFB1SmXfc6 oAMBQSTDrHeIcN4dD6t2PYDR02XuAq9ZoCLFqdRXc6eIZmco35g+RdhScF532ekLmWrE /UfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=VM3wn61H1VjiqZ/GdSQDgtkbXd9RLqWAj9a8bCiL1Hc=; b=Ez8CYZn7XvCXKv4mpSuim3LpHbJ/x6wRE8Eiw9j8n/I7La5FzM4kOyorylN0VT9T0+ 9Hm1MSzWyNj8c9vRZygIm+qBKBJUUyhf/L4c5ANBtedrrHR/MLwSiJOg8zQ9XpJfrWff XZZMX/20BAFrsLgLlGL/hUFM/sNNlKlKn/VnhoRcRYmrL1Dq4FC+PHB7xOD08A4pGyyR yVunfId9e7FrE4kZo2UkaQgL3CVftHGI9JqDDqV+RhxI7eONXCiXGvqUXcI8OO5MMZNB rPL9PPgMcyaUlYmgkc5QU3LfG3yO+Oiq9sAQn4pdgzr9MS+4JsZv8okc/U6nUkQz5W1K DwtQ== X-Gm-Message-State: AMCzsaWxoNTfP4YniFtbSYFVO36arZfFEn0FT8dj66hvBexF2X6kRA8d +9wcK8Ug9LMZA9fEFwFnMxFEf1D+ X-Google-Smtp-Source: ABhQp+S0Vf5mNCM+UPNpGW7czKuUnzUeI54Gr7UDyg664I+h7SyX7+XsqHhLXYl3mAhA3Rh2TlY5Mw== X-Received: by 10.223.156.133 with SMTP id d5mr2724036wre.29.1509351261241; Mon, 30 Oct 2017 01:14:21 -0700 (PDT) Received: from bidouze.vm.6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id m26sm14142400wrb.81.2017.10.30.01.14.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Oct 2017 01:14:20 -0700 (PDT) Date: Mon, 30 Oct 2017 09:14:09 +0100 From: =?iso-8859-1?Q?Ga=EBtan?= Rivet To: "Xu, Qian Q" Cc: "Lin, Xueqin" , "Zhang, Helin" , Thomas Monjalon , "Pei, Yulong" , "Peng, Yuan" , "dev@dpdk.org" , "Glynn, Michael J" , "Liu, Yu Y" Message-ID: <20171030081408.GG10890@bidouze.vm.6wind.com> References: <82F45D86ADE5454A95A89742C8D1410E3B7F050C@shsmsx102.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E3B7F050C@shsmsx102.ccr.corp.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) 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 08:14:22 -0000 Hi Xueqin, Thank you for the thorough test report. Multiple filings for this bug, please refer to the thread http://dpdk.org/ml/archives/dev/2017-October/080746.html Which will focus discussion. A first fix and a new proposition are available, please tell us if it works for you or if there are any other problem with either of the solutions. On Mon, Oct 30, 2017 at 07:25:20AM +0000, Xu, Qian Q wrote: > 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 probed. > > ? 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=igb_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= drv=i40evf unused=igb_uio > 0000:05:06.0 'XL710/X710 Virtual Function 154c' if= drv=i40evf unused=igb_uio > ./usertools/dpdk-devbind.py --bind=vfio-pci 81:02.0 81:06.0 > ./usertools/dpdk-devbind.py -s > 0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=igb_uio unused=vfio-pci > 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+ 1572' drv=igb_uio unused=vfio-pci > 0000:81:02.0 'XL710/X710 Virtual Function 154c' drv=vfio-pci unused=igb_uio > 0000:81:06.0 'XL710/X710 Virtual Function 154c' drv=vfio-pci unused=igb_uio > 2. up PF with testpmd, > ./x86_64-native-linuxapp-gcc/app/testpmd -l 23-27 -n 4 --socket-mem=1024,1024 --file-prefix=pf -w 81:00.0 -w 81:00.1 - -i --rxq=4 --txq=4 > 3. start VFs with testpmd, > ./x86_64-native-linuxapp-gcc/app/testpmd -l 28-32 -n 4 --socket-mem=1024,1024 --file-prefix=vf -w 81:02.0 -w 81:06.0 - -i --rxq=4 --txq=4 > EAL: Detected 88 lcore(s) > EAL: Some devices want iova as va but pa will be used because.. EAL: vfio-noiommu 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=179456, size=2176, socket=0 > USER1: create a new mbuf pool : n=179456, size=2176, socket=1 > 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 ; Peng, 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_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u 0x2 -j 9000\ > --config="(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 is urgent. > DPDK-4026 should meet same 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 bus. > They need to be publicly available for the PCI bus to be outside the > EAL. > > > Best regards, > Xueqin > -- Gaëtan Rivet 6WIND