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. Signed-off-by: Adrián Larumbe <[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]> Cc: [email protected] Cc: [email protected] --- Adrián Larumbe (2): drm/panthor: Add vm_bind region with kbo range overlap check drm/panthor: Fix comment to reflect actual struct field name drivers/gpu/drm/panthor/panthor_mmu.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) --- base-commit: 2afdfc658f7a7e9ee2a67ec6663922da9c799c53 change-id: 20260614-vm_bind_checks-46075ba069a0 Best regards, -- Adrián Larumbe <[email protected]>
