On 10/17/19 9:06 AM, Geert Uytterhoeven wrote: [...] >>>>> I suppose if your intent is to use inbound windows as a poor man's >>>>> IOMMU to prevent accesses to the holes, then yes you would list them >>>>> out. But I think that's wrong and difficult to maintain. You'd also >>>>> need to deal with reserved-memory regions too. >>>> >>>> What's the problem with that? The bootloader has all that information >>>> and can patch the DT correctly. In fact, in my specific case, I have >>>> platform which can be populated with differently sized DRAM, so the >>>> holes are also dynamically calculated ; there is no one DT then, the >>>> bootloader is responsible to generate the dma-ranges accordingly. >>> >>> The problems are it doesn't work: >>> >>> Your dma-mask and offset are not going to be correct. >>> >>> You are running out of inbound windows. Your patch does nothing to >>> solve that. The solution would be merging multiple dma-ranges entries >>> to a single inbound window. We'd have to do that both for dma-mask and >>> inbound windows. The former would also have to figure out which >>> entries apply to setting up dma-mask. I'm simply suggesting just do >>> that up front and avoid any pointless splits. >> >> But then the PCI device can trigger a transaction to non-existent DRAM >> and cause undefined behavior. Surely we do not want that ? > > The PCI device will trigger transactions to memory only when instructed > to do so by Linux, right? Hence if Linux takes into account chosen/memory > and dma-ranges, there is no problem? Unless of course the remote device initiates a transfer. And if the controller is programmed such that accesses to the missing DRAM in the holes are not filtered out by the controller, then the controller will gladly let the transaction through. Do we really want to let this happen ? [...] -- Best regards, Marek Vasut
