From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 005988042 for ; Thu, 4 Dec 2014 17:32:43 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga103.jf.intel.com with ESMTP; 04 Dec 2014 08:29:38 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,691,1406617200"; d="scan'208";a="493650299" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by orsmga003.jf.intel.com with ESMTP; 04 Dec 2014 08:27:55 -0800 Received: from irsmsx109.ger.corp.intel.com ([169.254.13.244]) by IRSMSX103.ger.corp.intel.com ([169.254.3.134]) with mapi id 14.03.0195.001; Thu, 4 Dec 2014 16:31:16 +0000 From: "Burakov, Anatoly" To: "Qiu, Michael" , Michael Qiu , "dev@dpdk.org" Thread-Topic: [PATCH] VFIO: Avoid to enable vfio while the module not loaded Thread-Index: AQHQD8G6joBiQX7ljU2i8wFFmoFrF5x/np/Q Date: Thu, 4 Dec 2014 16:31:15 +0000 Message-ID: References: <1417664219-19679-1-git-send-email-michael.qiu@intel.com> <533710CFB86FA344BFBF2D6802E60286C9CCC1@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <533710CFB86FA344BFBF2D6802E60286C9CCC1@SHSMSX101.ccr.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.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] VFIO: Avoid to enable vfio while the module not loaded 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: Thu, 04 Dec 2014 16:32:44 -0000 Hi Michael > But indeed, when try to unload both vfio and vfio_iommu_type1, > /dev/vfio/vfio still there, I'm also surprise. >=20 > My ENV is fedora20, kernel version 3.6.7-200 X86_64. >=20 > Believe or not, you can have a try, it seems a kernel issue. >=20 > When you unload both two modules, then open /dev/vfio/vfio, you will find > it can be opened with no errors(but this time both two modules loaded > automatically, strange enough) >=20 Thanks to Sergio, we found a most likely cause for this. This patch to Linu= x kernel by Alex Williamson of Red Hat: https://lkml.org/lkml/2013/12/12/421 it seems, however, that it has been merged into 3.14. Your kernel, by your = own admission, is 3.6. Are you sure this is the right kernel version? Becau= se my own machine has Fedora 18 with a 3.11 kernel, and it (correctly) does= not display this behavior. So unless Fedora 20 backported those changes to= kernel 3.6, this shouldn't happen on your set up. (but it doesn't really m= atter, just FYI - the patch still should be fixed and resubmitted, just as = we discussed) Thanks, Anatoly