Gaurav Batra fa5d374f6b powerpc/pseries/iommu: memory notifier incorrectly adds TCEs for pmemory ... [ Upstream commit 6aa989ab2b ] iommu_mem_notifier() is invoked when RAM is dynamically added/removed. This notifier call is responsible to add/remove TCEs from the Dynamic DMA Window (DDW) when TCEs are pre-mapped. TCEs are pre-mapped only for RAM and not for persistent memory (pmemory). For DMA buffers in pmemory, TCEs are dynamically mapped when the device driver instructs to do so. The issue is 'daxctl' command is capable of adding pmemory as "System RAM" after LPAR boot. The command to do so is - daxctl reconfigure-device --mode=system-ram dax0.0 --force This will dynamically add pmemory range to LPAR RAM eventually invoking iommu_mem_notifier(). The address range of pmemory is way beyond the Max RAM that the LPAR can have. Which means, this range is beyond the DDW created for the device, at device initialization time. As a result when TCEs are pre-mapped for the pmemory range, by iommu_mem_notifier(), PHYP HCALL returns H_PARAMETER. This failed the command, daxctl, to add pmemory as RAM. The solution is to not pre-map TCEs for pmemory. Signed-off-by: Gaurav Batra <gbatra@linux.ibm.com> Tested-by: Donet Tom <donettom@linux.ibm.com> Reviewed-by: Donet Tom <donettom@linux.ibm.com> Signed-off-by: Madhavan Srinivasan <maddy@linux.ibm.com> Link: https://patch.msgid.link/20250130183854.92258-1-gbatra@linux.ibm.com Signed-off-by: Sasha Levin <sashal@kernel.org>		2025-06-04 14:42:11 +02:00
..
4xx
8xx
40x
44x
52xx
82xx
83xx
85xx
86xx
512x
amigaone
book3s
cell	spufs: fix a leak in spufs_create_context()	2025-04-10 14:37:38 +02:00
chrp
embedded6xx
maple
microwatt
pasemi
powermac
powernv
ps3
pseries	powerpc/pseries/iommu: memory notifier incorrectly adds TCEs for pmemory	2025-06-04 14:42:11 +02:00
fsl_uli1575.c
Kconfig
Kconfig.cputype
Makefile