On Thu, 6 Feb 2025, Orzel, Michal wrote: > On 06/02/2025 02:08, Stefano Stabellini wrote: > > From: Henry Wang <[email protected]> > > > > 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. > > > > Signed-off-by: Henry Wang <[email protected]> > > Signed-off-by: Stefano Stabellini <[email protected]> > > Acked-by: Michal Orzel <[email protected]> > This patch has already been committed (see 0a0f30c1b55e) and later on fixed > (see 988f1c7e1f40). > > DO NOT COMMIT.
Thanks Michal!! I'll take off the series.
