On Sat, 04 Jul 2026 05:46:45 +0100, Adrián Larumbe <[email protected]> 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. > > Fixes: tag and reference the relevant sparse binding support commit.
Just realised this was a placeholder I left before I went looking for the right commit hash for the following tag. Seems that checkpatch.pl wouldn't catch it either. -- Adrián Larumbe <[email protected]>
