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 62C87B0B7 for ; Tue, 17 Jun 2014 00:23:56 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 16 Jun 2014 15:18:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,489,1400050800"; d="scan'208";a="558489993" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by orsmga002.jf.intel.com with ESMTP; 16 Jun 2014 15:24:10 -0700 Received: from irsmsx154.ger.corp.intel.com (163.33.192.96) by IRSMSX103.ger.corp.intel.com (163.33.3.157) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 16 Jun 2014 23:24:09 +0100 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.58]) by IRSMSX154.ger.corp.intel.com ([169.254.12.14]) with mapi id 14.03.0123.003; Mon, 16 Jun 2014 23:24:09 +0100 From: "Richardson, Bruce" To: "dev@dpdk.org" Thread-Topic: vfio detection Thread-Index: Ac+Jr+QsX/7njye/SDa+CSH3FJFocA== Date: Mon, 16 Jun 2014 22:24:09 +0000 Message-ID: <59AF69C657FD0841A61C55336867B5B01AA36B6E@IRSMSX103.ger.corp.intel.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [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: Mon, 16 Jun 2014 22:23:57 -0000 Hi all, Now that vfio support has merged into the dpdk.org mainline, I'm seeing a n= umber of issues with running applications, and I'm hoping someone can expla= in the observed behaviour. I have a number of NIC ports which were working correctly yesterday and are= bound correctly to the igb_uio driver - and I want to keep using them thro= ugh the igb_uio driver for now, not vfio. However, whenever I run a dpdk ap= plication today, I find that the vfio kernel module is getting loaded 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 the vfio dr= iver when I just want to continue using igb_uio which works fine? Secondly, then, when testpmd or any other app loads, it automatically tries= to map the NIC using vfio and then aborts on the very first NIC port when = it fails to do so. This a) prevents the port from being mapped using igb_ui= o, and b) for ports which are meant to stay under linux control, forces me = to start enumerating ports using blacklist or whitelisting, rather than hav= ing things "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 this by design and expected, because it seems a major regression = in usability? Regards, /Bruce