From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 76C262BBE; Fri, 15 Sep 2017 10:42:50 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 538EF20DBD; Fri, 15 Sep 2017 04:42:47 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 15 Sep 2017 04:42:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=8h0yWJw7/KtMJmI vNmF7Ib3fmsjvz5XivIbGcDQX7QI=; b=XAS/HB79HqTTzN/SrVm0hL/8MBV+MX8 zQZ59Tel08DMQY/gz7pc6ZWvbYejTOv8AKO6K0i3bJE+tWQotpkI2ceMAgxjCfeR MB1T5lkCxHjYVck3E5Wh0VRGxqlSjci5XctHCfOjbe8IJxSyprXROdP+/encscTq mOI5hoo6FLuE= 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-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=8h0yWJw7/KtMJmIvNmF7Ib3fmsjvz5XivIbGcDQX7QI=; b=gOJ92jlc Si1kh7UbpoKeIE/TjXCareb1Wp0exDd1DKLZkQeEANiVaBZiu45kS1Roo0arm9C6 lcW3aQh7k762s80u5SIOpz6xbLEDE3AjUzTC1Pautyr3g8lEXxZPuXOWqtJXBSEj 04HCZfJl/D9UuuEgDWn7204cCgkOIca3/m6lWJ1hEfc+w2TijuuHYUza3QafTf0K nM3Ew3A1d780eqTalE0PowobzRwT/K4RoDgHI3+SmfXMgbnWlrqdhqQQbh26r4gm jQu2uW7qvTZTuFDBFmIZxVwWmDZeZmyWLZv61oIF1YC4DWn0xVDiX0ldWn6mZxTm Oh4A8lddiShh6Q== X-ME-Sender: <xms:h5K7WcYO7M5yLqfDtEqZiXfkulvZnDTk7sPG2SPHHAPQe57PQEhxkw> X-Sasl-enc: i9aq5b2gsYTT38sn0cjioiuD8Gw5fsix3I70TX4L+6qf 1505464967 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id F00C97F96A; Fri, 15 Sep 2017 04:42:46 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: "Yang, Qiming" <qiming.yang@intel.com> Cc: dev@dpdk.org, "Tan, Jianfeng" <jianfeng.tan@intel.com>, "Thotton, Shijith" <Shijith.Thotton@cavium.com>, "Hu, Xuekun" <xuekun.hu@intel.com>, "Yigit, Ferruh" <ferruh.yigit@intel.com>, "Patil, Harish" <Harish.Patil@cavium.com>, Gregory Etelson <gregory@weka.io>, stable@dpdk.org Date: Fri, 15 Sep 2017 10:42:46 +0200 Message-ID: <1836615.UbEDzhAzGh@xps> In-Reply-To: <F5DF4F0E3AFEF648ADC1C3C33AD4DBF16F7EA3EB@SHSMSX151.ccr.corp.intel.com> References: <F5DF4F0E3AFEF648ADC1C3C33AD4DBF16F7E0E71@SHSMSX101.ccr.corp.intel.com> <D5DED7B9.160793%Harish.Patil@cavium.com> <F5DF4F0E3AFEF648ADC1C3C33AD4DBF16F7EA3EB@SHSMSX151.ccr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-stable] [dpdk-dev] vf init issue with patch igb_uio: issue FLR during open and release of device file X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches <stable.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/stable>, <mailto:stable-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/stable/> List-Post: <mailto:stable@dpdk.org> List-Help: <mailto:stable-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/stable>, <mailto:stable-request@dpdk.org?subject=subscribe> X-List-Received-Date: Fri, 15 Sep 2017 08:42:50 -0000 Hi 15/09/2017 10:04, Yang, Qiming: > Hi, Thomas > We meet a urgent issue because of Shijith's patch. > When use DPDK version 17.08, DPDK VF driver and kernel PF driver, i40e, ixgbe and qede(Harish said) VF all meet initial failure. This patch has been integrated in DPDK 17.08-rc2 (2 months ago). Why a so obvious issue is discovered only now? > This issue only occurred when use 17.08 igb_uio, vfio-pci and 17.05 igb_uio all works well. > Considering this issue will block our vf driver develop and test work, could we revert this patch first and find another appropriate way? We need to be sure the revert is the right solution because it will be backported to the stable 17.08 release. Shijith suggests to "try removing pci_reset_function from igbuio_pci_open." Can we try this first? Are we sure the bug is not in new firmwares?