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 D8CCE6AAE for ; Fri, 5 Dec 2014 05:02:56 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP; 04 Dec 2014 20:02:55 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,862,1389772800"; d="scan'208";a="425338309" Received: from kmsmsx152.gar.corp.intel.com ([172.21.73.87]) by FMSMGA003.fm.intel.com with ESMTP; 04 Dec 2014 19:52:33 -0800 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by KMSMSX152.gar.corp.intel.com (172.21.73.87) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 5 Dec 2014 12:01:59 +0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.110]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.182]) with mapi id 14.03.0195.001; Fri, 5 Dec 2014 12:01:57 +0800 From: "Qiu, Michael" To: "Burakov, Anatoly" , Michael Qiu , "dev@dpdk.org" Thread-Topic: [PATCH] VFIO: Avoid to enable vfio while the module not loaded Thread-Index: AQHQD8G6SQyqYdhz8kSLOFnIk6ncxw== Date: Fri, 5 Dec 2014 04:01:57 +0000 Message-ID: <533710CFB86FA344BFBF2D6802E60286C9CF85@SHSMSX101.ccr.corp.intel.com> References: <1417664219-19679-1-git-send-email-michael.qiu@intel.com> <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: [10.239.127.40] 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: Fri, 05 Dec 2014 04:02:57 -0000 On 12/5/2014 12:31 AM, Burakov, Anatoly wrote:=0A= > Hi Michael=0A= >=0A= >> But indeed, when try to unload both vfio and vfio_iommu_type1,=0A= >> /dev/vfio/vfio still there, I'm also surprise.=0A= >>=0A= >> My ENV is fedora20, kernel version 3.6.7-200 X86_64.=0A= >>=0A= >> Believe or not, you can have a try, it seems a kernel issue.=0A= >>=0A= >> When you unload both two modules, then open /dev/vfio/vfio, you will fin= d=0A= >> it can be opened with no errors(but this time both two modules loaded=0A= >> automatically, strange enough)=0A= >>=0A= > Thanks to Sergio, we found a most likely cause for this. This patch to Li= nux kernel by Alex Williamson of Red Hat:=0A= >=0A= > https://lkml.org/lkml/2013/12/12/421=0A= >=0A= > it seems, however, that it has been merged into 3.14. Your kernel, by you= r own admission, is 3.6. Are you sure this is the right kernel version? Bec= ause my own machine has Fedora 18 with a 3.11 kernel, and it (correctly) do= es not =0A= =0A= Sorry, the kernel version is 3.16 :), just make a mistake :)=0A= =0A= Thanks,=0A= Michael=0A= > display this behavior. So unless Fedora 20 backported those changes to ke= rnel 3.6, this shouldn't happen on your set up. (but it doesn't really matt= er, just FYI - the patch still should be fixed and resubmitted, just as we = discussed)=0A= >=0A= > Thanks,=0A= > Anatoly=0A= >=0A= =0A=