Re: [PATCH v2 1/2] drm/panthor: Add vm_bind region with kbo range overlap check

[Adrián Larumbe]

On 2026-06-19 14:59:06+02:00, Boris Brezillon wrote:
> On Fri, 19 Jun 2026 13:41:22 +0100
> Adrián Larumbe <adrian.larumbe@xxxxxxxxxxxxx> wrote:
> 
> > When a VM is created, caller has to specify the range of the address space
> > carve-out set aside for mapping kernel BO's. That means vm_bind mappings of
> > UM-exposed BO's should not intersect with that region, but at the moment
> > we're not checking this.
> > 
> > At first, I thought of giving these values to drm_gpuvm_init() through its
> > reserve_{offset, range} arguments, but it turns out that is meant for VM
> > address spans that are not managed through the usual drm_gpuvm split/merge
> > circuit, so storing the end of the user VA range at VM creation time and
> > doing a quick check in the vm_bind ioctl path was the simplest workaround.
> > 
> > Signed-off-by: Adrián Larumbe <adrian.larumbe@xxxxxxxxxxxxx>
> 
> Ah, we need a Fixes tag here.

Fixes: 647810ec2476 ("drm/panthor: Add the MMU/VM logical block")