From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 3820C1B28D for ; Thu, 15 Feb 2018 11:28:36 +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 fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Feb 2018 02:28:35 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,516,1511856000"; d="scan'208";a="175401626" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.237.220.71]) ([10.237.220.71]) by orsmga004.jf.intel.com with ESMTP; 15 Feb 2018 02:28:34 -0800 To: Ravi Kerur Cc: dev@dpdk.org References: <8ddb30a3-1253-ff60-20bb-b735fef5a91c@intel.com> <4a54fe58-02d8-07ef-b706-f747383f4985@intel.com> From: "Burakov, Anatoly" Message-ID: <3b6d6cfc-7e2e-70ee-e059-aa31dc23c93b@intel.com> Date: Thu, 15 Feb 2018 10:28:33 +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: 8bit 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, 15 Feb 2018 10:28:37 -0000 On 14-Feb-18 8:00 PM, Ravi Kerur wrote: > > Earlier I was focusing only on DMAR errors and I might have said 'it > worked' when I didn't notice them on host when dpdk was started on > guest. When trying to send packets out of that interface from guest I > did see DMAR errors. I am attaching information you requested.  I have > enabled log-level=8 and files contain dpdk EAL/PMD logs as well. Great, now we're on the same page. > > Snippets below > > on host, DMAR fault address from dmesg > > [351576.998109] DMAR: DRHD: handling fault status reg 702 > [351576.998113] DMAR: [DMA Read] Request device [04:10.0] fault addr > 257617000 [fault reason 06] PTE Read access is not set > > on guest (dump phys_mem_layout) > > Segment 235: phys:0x257600000, len:2097152, virt:0x7fce87e00000, > socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0 > ... > PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7fce87e0f4c0 > sw_sc_ring=0x7fce87e07380 hw_ring=0x7fce87e17600 dma_addr=0x257617600 > PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7fce89c67d40 > sw_sc_ring=0x7fce89c5fc00 hw_ring=0x7fce89c6fe80 dma_addr=0x25406fe80 > ... > To me this looks like host (i.e. either QEMU or the PF driver) is trying to do DMA using guest-physical (and not host-physical). I'm not too well-versed in how QEMU works, but i'm pretty sure that's not supposed to happen. Is PF also bound to DPDK, or are you using native Linux ixgbe driver? -- Thanks, Anatoly