From mboxrd@z Thu Jan 1 00:00:00 1970 From: Subash Patel Subject: Re: [PATCHv7 9/9] ARM: dma-mapping: add support for IOMMU mapper Date: Thu, 22 Mar 2012 19:29:42 +0530 Message-ID: <4F6B304E.5010402@gmail.com> References: <1330527862-16234-1-git-send-email-m.szyprowski@samsung.com> <1330527862-16234-10-git-send-email-m.szyprowski@samsung.com> <4F688B2D.20808@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-samsung-soc-owner@vger.kernel.org To: KyongHo Cho Cc: Marek Szyprowski , linux-arm-kernel@lists.infradead.org, linaro-mm-sig@lists.linaro.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-samsung-soc@vger.kernel.org, iommu@lists.linux-foundation.org, Shariq Hasnain , Arnd Bergmann , Benjamin Herrenschmidt , Krishna Reddy , Kyungmin Park , Andrzej Pietrasiewicz , Russell King - ARM Linux , Chunsang Jeong List-Id: linux-arch.vger.kernel.org Hi KyongHo, On 03/21/2012 05:26 AM, KyongHo Cho wrote: > On Tue, Mar 20, 2012 at 10:50 PM, Subash Patel wrote: >> Sorry for digging this very late. But as part of integrating dma_map v7& >> sysmmu v12 on 3.3-rc5, I am facing below issue: >> >> a) By un-selecting IOMMU in menu config, I am able to allocate memory in >> vb2-dma-contig >> >> b) When I enable SYSMMU support for the IP's, I am receiving below fault: >> >> Unhandled fault: external abort on non-linefetch (0x818) at 0xb6f55000 >> >> I think this has something to do with the access to the SYSMMU registers for >> writing the page table. Has anyone of you faced this issue while testing >> these(dma_map+iommu) patches on kernel mentioned above? This must be >> something related to recent changes, as I didn't have issues with these >> patches on 3.2 kernel. >> > > 0xb6f55000 is not an address of SYSMMU register if your kernel starts > at 0xc0000000. > > Can you tell me any detailed information or situation? I hate to say this, but I am not able to catch the fault location even with JTAG. Once the fault comes, the debugger looses all control over. I think now possible method is reproduction at your end :) > > Regards, > > KyongHo. Regards, Subash From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx148.postini.com [74.125.245.148]) by kanga.kvack.org (Postfix) with SMTP id 808436B007E for ; Thu, 22 Mar 2012 09:59:50 -0400 (EDT) Received: by yhr47 with SMTP id 47so2228161yhr.14 for ; Thu, 22 Mar 2012 06:59:49 -0700 (PDT) Message-ID: <4F6B304E.5010402@gmail.com> Date: Thu, 22 Mar 2012 19:29:42 +0530 From: Subash Patel MIME-Version: 1.0 Subject: Re: [PATCHv7 9/9] ARM: dma-mapping: add support for IOMMU mapper References: <1330527862-16234-1-git-send-email-m.szyprowski@samsung.com> <1330527862-16234-10-git-send-email-m.szyprowski@samsung.com> <4F688B2D.20808@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: KyongHo Cho Cc: Marek Szyprowski , linux-arm-kernel@lists.infradead.org, linaro-mm-sig@lists.linaro.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-samsung-soc@vger.kernel.org, iommu@lists.linux-foundation.org, Shariq Hasnain , Arnd Bergmann , Benjamin Herrenschmidt , Krishna Reddy , Kyungmin Park , Andrzej Pietrasiewicz , Russell King - ARM Linux , Chunsang Jeong Hi KyongHo, On 03/21/2012 05:26 AM, KyongHo Cho wrote: > On Tue, Mar 20, 2012 at 10:50 PM, Subash Patel wrote: >> Sorry for digging this very late. But as part of integrating dma_map v7& >> sysmmu v12 on 3.3-rc5, I am facing below issue: >> >> a) By un-selecting IOMMU in menu config, I am able to allocate memory in >> vb2-dma-contig >> >> b) When I enable SYSMMU support for the IP's, I am receiving below fault: >> >> Unhandled fault: external abort on non-linefetch (0x818) at 0xb6f55000 >> >> I think this has something to do with the access to the SYSMMU registers for >> writing the page table. Has anyone of you faced this issue while testing >> these(dma_map+iommu) patches on kernel mentioned above? This must be >> something related to recent changes, as I didn't have issues with these >> patches on 3.2 kernel. >> > > 0xb6f55000 is not an address of SYSMMU register if your kernel starts > at 0xc0000000. > > Can you tell me any detailed information or situation? I hate to say this, but I am not able to catch the fault location even with JTAG. Once the fault comes, the debugger looses all control over. I think now possible method is reproduction at your end :) > > Regards, > > KyongHo. Regards, Subash -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: subashrp@gmail.com (Subash Patel) Date: Thu, 22 Mar 2012 19:29:42 +0530 Subject: [PATCHv7 9/9] ARM: dma-mapping: add support for IOMMU mapper In-Reply-To: References: <1330527862-16234-1-git-send-email-m.szyprowski@samsung.com> <1330527862-16234-10-git-send-email-m.szyprowski@samsung.com> <4F688B2D.20808@gmail.com> Message-ID: <4F6B304E.5010402@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi KyongHo, On 03/21/2012 05:26 AM, KyongHo Cho wrote: > On Tue, Mar 20, 2012 at 10:50 PM, Subash Patel wrote: >> Sorry for digging this very late. But as part of integrating dma_map v7& >> sysmmu v12 on 3.3-rc5, I am facing below issue: >> >> a) By un-selecting IOMMU in menu config, I am able to allocate memory in >> vb2-dma-contig >> >> b) When I enable SYSMMU support for the IP's, I am receiving below fault: >> >> Unhandled fault: external abort on non-linefetch (0x818) at 0xb6f55000 >> >> I think this has something to do with the access to the SYSMMU registers for >> writing the page table. Has anyone of you faced this issue while testing >> these(dma_map+iommu) patches on kernel mentioned above? This must be >> something related to recent changes, as I didn't have issues with these >> patches on 3.2 kernel. >> > > 0xb6f55000 is not an address of SYSMMU register if your kernel starts > at 0xc0000000. > > Can you tell me any detailed information or situation? I hate to say this, but I am not able to catch the fault location even with JTAG. Once the fault comes, the debugger looses all control over. I think now possible method is reproduction at your end :) > > Regards, > > KyongHo. Regards, Subash