From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 0CAE81B29E for ; Tue, 13 Feb 2018 15:31:45 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Feb 2018 06:31:44 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,507,1511856000"; d="scan'208";a="34340702" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.237.220.71]) ([10.237.220.71]) by orsmga002.jf.intel.com with ESMTP; 13 Feb 2018 06:31:43 -0800 To: Ravi Kerur Cc: dev@dpdk.org References: <8ddb30a3-1253-ff60-20bb-b735fef5a91c@intel.com> From: "Burakov, Anatoly" Message-ID: <4a54fe58-02d8-07ef-b706-f747383f4985@intel.com> Date: Tue, 13 Feb 2018 14:31:43 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 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: Tue, 13 Feb 2018 14:31:46 -0000 On 12-Feb-18 10:00 PM, Ravi Kerur wrote: > > Let me just give you what has been tested and working/nonworking > scenarios. Some of your questions might get answered as well. > Test bed is very simple with 2 VF's created under IXGBE PF on > host with one VF interface added to ovs-bridge on host and > another VF interface given to guest. Test connectivity between > VF's via ping. > > Host and guest -- Kernel 4.9 > Host -- Qemu 2.11.50 (tried both released 2.11 and tip of the > git (2.11.50)) > DPDK -- 17.05.1 on host and guest > Host and guest -- booted with GRUB intel_iommu=on (which enables > IOMMU). Have tried with "iommu=on and intel_iommu=on" as well, > but iommu=on is not needed when intel_iommu=on is set. > > Test-scenario-1: Host -- ixgbe_vf driver, Guest ixgbe_vf driver > ping works > Test-scenario-2: Host -- DPDK vfio-pci driver, Guest ixgbe_vf > driver ping works > Test-scenario-3: Host -- DPDK vfio-pci driver, Guest DPDK > vfio-pci driver, DMAR errors seen on host, ping doesn't work > > > OK, that makes it clearer, thanks. Does the third scenario work in > other DPDK versions? > > > No. Tried 16.11 same issue on guest and works fine on host. > > So now we've moved from "this worked on 16.11" to "this never worked". It would be good to see output of rte_dump_physmem_layout() on both host and guest, and check which address triggers the DMAR error (i.e. if the physical address is present in mappings for either DPDK process). -- Thanks, Anatoly