From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 765F7271 for ; Thu, 1 Feb 2018 11:10:16 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2018 02:10:15 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,443,1511856000"; d="scan'208";a="170840648" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.237.220.145]) ([10.237.220.145]) by orsmga004.jf.intel.com with ESMTP; 01 Feb 2018 02:10:14 -0800 To: Ravi Kerur Cc: dev@dpdk.org References: <8ddb30a3-1253-ff60-20bb-b735fef5a91c@intel.com> <10911b54-57ee-370b-a4f7-f34accf4811e@intel.com> From: "Burakov, Anatoly" Message-ID: <3464b900-8648-c128-e959-dc60a8883a2d@intel.com> Date: Thu, 1 Feb 2018 10:10:14 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] IXGBE, IOMMU DMAR DRHD handling fault issue X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 10:10:17 -0000 On 31-Jan-18 9:51 PM, Ravi Kerur wrote: > > Hi Anatoly, > > Thanks. I am following wiki link below which uses vIOMMU with DPDK as a > use-case and instantiate VM as specified with Q35 chipset in Qemu. > > https://wiki.qemu.org/Features/VT-d > > Qemu-version is 2.11 > Host kernel 4.9 > Guest kernel 4.4 > > I can only guess that guest kernel needs an upgrade in my setup to work > correctly, if versions on my setup rings a bell on not having support > kindly let me know. > > When 'modprobe vfio enable_unsafe_noiommu_node=Y' is executed on guest I > get following error > ... > vfio: unknown parameter 'enable_unsafe_noiommu_node' ignored > ... > > in guest. > > Thanks. AFAIK kernel 4.4 should have noiommu mode - it was introduced in 3.1x days. However, in order for that to work, kernel also has to be built with this mode enabled. My guess is, whoever is the supplier of your kernel, did not do that. You should double-check the kernel configuration of your distribution. However, if you have vIOMMU in QEMU, you shouldn't need noiommu mode - "regular" vfio should work fine. noiommu mode should only be needed if you know you don't have IOMMU enabled in your kernel, and even if you can't enable it, you can still use igb_uio. -- Thanks, Anatoly