On Mon, 2021-02-08 at 12:59 +0000, Peter Maydell wrote: > I just suggested something on another thread: call > memory_region_find() > and then look at the offset_within_address_space field of the > returned > MemoryRegionSection. I think that should get you the offset of the > transport within the system address space regardless of how much > use of containers and other oddball mappings are involved. (If the > transport is not mapped into the system address space at all then > you'll get its offset within whatever that other address space is, > but I think we can reasonably ignore that unlikely corner case.)
Thanks for your suggestions, I have tried it on both arm virt & the Xilinx platform works perfectly. I have upload a new patch v4 for it. -- schspa <[email protected]>
