> On 20 May 2024, at 12:24, Michal Orzel <michal.or...@amd.com> wrote: > > Hi Henry, > > +CC: Luca > > On 17/05/2024 05:21, Henry Wang wrote: >> >> >> Currently, users are allowed to map static shared memory in a >> non-direct-mapped way for direct-mapped domains. This can lead to >> clashing of guest memory spaces. Also, the current extended region >> finding logic only removes the host physical addresses of the >> static shared memory areas for direct-mapped domains, which may be >> inconsistent with the guest memory map if users map the static >> shared memory in a non-direct-mapped way. This will lead to incorrect >> extended region calculation results. >> >> To make things easier, add restriction that static shared memory >> should also be direct-mapped for direct-mapped domains. Check the >> host physical address to be matched with guest physical address when >> parsing the device tree. Document this restriction in the doc. > I'm ok with this restriction. > > @Luca, do you have any use case preventing us from making this restriction?
Hi Michal, Henry, I think it’s sensible, I don’t think we have any use case for direct-mapped domains using non direct mapped static shared memory. Cheers, Luca
