> -----Original Message----- > From: Felipe Contreras [mailto:[email protected]] > Sent: Sunday, October 10, 2010 12:33 PM > To: Guzman Lugo, Fernando > Cc: [email protected]; [email protected]; > [email protected]; Menon, Nishanth; > [email protected]; [email protected]; > [email protected]; [email protected]; > [email protected] > Subject: Re: [PATCHv3 00/11] staging tidspbridge: iommu migration > > On Tue, Oct 5, 2010 at 11:35 PM, Fernando Guzman Lugo > <[email protected]> wrote: > > This set of patches remove the dspbridge custom mmu > implementation and > > use iommu module instead. > > I have tried this, it works for simple tests, but not real use-cases. > I applied all your iommu patches. How did you test this?
Have you applied: - "scatterlist: define SG chain for arm architecture" - "iovmm: replace __iounmap with omap_iounmap" - "iovmm: add superpages support to fixed da address" - "iovmm: IVA2 MMU range is from 0x11000000 to 0xFFFFFFFF" - "iovmm: no gap checking for fixed address" Also make sure your baseline have this patch: - "omap:iommu-load cam register before flushing the entry" What kind of error are you getting? I don't have a complete framework to test MM testcases at this moment I did not stress test but a bridge level, and they were good, just some Mailbox issues beucase of the lack of some patches. So I was waiting All missing patches are merge in order to do more stressing testing because I think there is some race conditions in iommu module that need to be fixed. You can email me the case and erros you are facing privately and I will Check them, maybe it is because of missing patches. Regards, Fernando. > > -- > Felipe Contreras > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
