From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 034A758D3 for ; Tue, 17 Jun 2014 10:39:47 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 17 Jun 2014 01:40:03 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,492,1400050800"; d="scan'208";a="549082334" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by fmsmga001.fm.intel.com with ESMTP; 17 Jun 2014 01:40:02 -0700 Received: from irsmsx107.ger.corp.intel.com (163.33.3.99) by IRSMSX102.ger.corp.intel.com (163.33.3.155) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 17 Jun 2014 09:40:01 +0100 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.245]) by IRSMSX107.ger.corp.intel.com ([169.254.10.208]) with mapi id 14.03.0123.003; Tue, 17 Jun 2014 09:40:01 +0100 From: "Burakov, Anatoly" To: "Richardson, Bruce" , "dev@dpdk.org" Thread-Topic: vfio detection Thread-Index: Ac+Jr+QsX/7njye/SDa+CSH3FJFocAAVxw1Q Date: Tue, 17 Jun 2014 08:40:00 +0000 Message-ID: References: <59AF69C657FD0841A61C55336867B5B01AA36B6E@IRSMSX103.ger.corp.intel.com> In-Reply-To: <59AF69C657FD0841A61C55336867B5B01AA36B6E@IRSMSX103.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] vfio detection X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 08:39:48 -0000 Hi Bruce, > I have a number of NIC ports which were working correctly yesterday and a= re > bound correctly to the igb_uio driver - and I want to keep using them > through the igb_uio driver for now, not vfio. However, whenever I run a > dpdk application today, I find that the vfio kernel module is getting loa= ded > each time - even after I manually remove it, and verify that it has been > removed by checking lsmod. Is this expected? If so, why are we loading th= e > vfio driver when I just want to continue using igb_uio which works fine? Can you elaborate a bit on what do you mean by "loading vfio driver"? Do yo= u mean the vfio-pci kernel gets loaded by DPDK? I certainly didn't put in a= ny code that would automatically load that driver, and certainly not bindin= g devices to it. > Secondly, then, when testpmd or any other app loads, it automatically tri= es > to map the NIC using vfio and then aborts on the very first NIC port when= it > fails to do so. This shouldn't happen, unless you have a device bound to VFIO and have anot= her device in the same IOMMU group that is bound to something else. Can you= provide a log of what you are seeing? > This a) prevents the port from being mapped using igb_uio, and > b) for ports which are meant to stay under linux control, forces me to st= art > enumerating ports using blacklist or whitelisting, rather than having thi= ngs > "just work" on a properly configured system as before, i.e. if a port is = bound > to igb_uio or vfio it is used, if not bound, it is ignored. Again, is thi= s by design > and expected, because it seems a major regression in usability? I think automatic port unbinding and binding was removed, so this again sho= uldn't happen at all. It would be useful to have logs for all of these described situations, beca= use we certainly didn't encounter any of that during the validation cycle. Best regards, Anatoly Burakov DPDK SW Engineer =20