On Tue, Apr 14, 2015 at 3:31 PM, Yong Wu <yong.wu@xxxxxxxxxxxx> wrote: >> >> >> >> > + >> >> > + piommu->protect_va = devm_kmalloc(piommu->dev, MTK_PROTECT_PA_ALIGN*2, >> >> >> >> style: Operators like * should have space on both sides. >> >> >> >> > + GFP_KERNEL); >> >> >> >> Shouldn't dma_alloc_coherent() be used for this? >> > We don't care the data in it. I think they are the same. Could you >> > help tell me why dma_alloc_coherent may be better. >> >> Can you guarantee that at the time you allocate the memory using >> devm_kmalloc() the memory is not dirty (i.e. some write back data are >> stored in CPU cache) and is not going to be written back in some time, >> overwriting data put there by IOMMU hardware? >> > As I noted in the function "mtk_iommu_hw_init": > > /* protect memory,HW will write here while translation fault */ > protectpa = __virt_to_phys(piommu->protect_va); > > We don’t care the content of this buffer, It is ok even though its > data is dirty. > It seem to be a the protect memory. While a translation fault > happened, The iommu HW will overwrite here instead of writing to the > fault physical address which may be 0 or some random address. > Do you mean that it's just a dummy page for hardware behind the IOMMU to access when the mapping is not available? How would that work with potential on demand paging when the hardware needs to be blocked until the mapping is created? Best regards, Tomasz -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
