Hi Pierrick, Tao, On 1/8/26 3:22 AM, Tao Tang wrote: > Hi Eric, > > On 2026/1/8 02:32, Eric Auger wrote: >> Hi Pierrick, >> >> On 12/17/25 12:57 AM, Pierrick Bouvier wrote: >>> This will be used to access non-secure and secure memory. Secure >>> support >>> and Granule Protection Check (for RME) for SMMU need to access secure >>> memory. >>> >>> As well, it allows to remove usage of global address_space_memory, >>> allowing different SMMU instances to have a specific view of memory. >>> >>> User creatable SMMU are handled as well for virt machine, >>> by setting the memory properties when device is plugged in. >> Will Tao's [RFC v3 08/21] hw/arm/smmuv3: Add separate address space for >> secure SMMU accesses >> be rebased on top of that. How does it cooperate? >> >> Thanks >> >> Eric > Yes — my latest Secure SMMU V4 will be based on Pierrick’s > memory/secure-memory property infrastructure. > > In my earlier [RFC v3 08/21] implementation, I made the Secure > AddressSpace global, which may be a real design problem (notably for > multiple SMMU instances). I have already rebased and updated my V4 > code on top of Pierrick’s patch; it’s currently under debugging. OK thank you for the confirmation
Eric > > Thanks, > Tao >
