Just a quick check to make sure user-supplied vm_bind regions aren't clashing with the region reserved for kernel bo's.
I tried to introduce a similar check for panthor_vm_alloc_va(), to throw back an error when mappings of kernel bo's against specific addresses fall within the auto_va region. However that is not possible, since there's one FW region that must be mapped right at CSF_MCU_SHARED_REGION_START. That is usually not a problem, since drm_mm_insert_node_in_range() will pick the next one available. v3 also comes with an early bind range overflow check for sparse mappings. Signed-off-by: Adrián Larumbe <[email protected]> --- Changes in v3: - Fixed off-by-one error for user va range calculations. - Added new commit for panthor_vm_prepare_unmap_op_ctx to take a whole operation. - Added commit with bind range early overflow check. - Link to v2: https://patch.msgid.link/[email protected] Changes in v2: - Simplified user VA range with kernel BO range overlap to a single statement. - Link to v1: https://patch.msgid.link/[email protected] To: Boris Brezillon <[email protected]> To: Steven Price <[email protected]> To: Liviu Dudau <[email protected]> To: Maarten Lankhorst <[email protected]> To: Maxime Ripard <[email protected]> To: Thomas Zimmermann <[email protected]> To: David Airlie <[email protected]> To: Simona Vetter <[email protected]> To: Heiko Stuebner <[email protected]> To: Grant Likely <[email protected]> To: Adrián Larumbe <[email protected]> Cc: [email protected] Cc: [email protected] --- Adrián Larumbe (4): drm/panthor: Add vm_bind region with kbo range overlap check drm/panthor: Fix comment to reflect actual struct field name drm/panthor: Have prepare_unmap_op_ctx receive a whole vm_bind op drm/panthor: Check for sparse binding range overflow drivers/gpu/drm/panthor/panthor_mmu.c | 42 +++++++++++++++++++++++++++-------- 1 file changed, 33 insertions(+), 9 deletions(-) --- base-commit: 8fca3d8dbebf8d960dad7b10db3cb4a61139454b change-id: 20260614-vm_bind_checks-46075ba069a0 Best regards, -- Adrián Larumbe <[email protected]>
