search for: nouveau_uvmm_vmm_get

...d ops take the same path, so no risk for those to modify the > VA space either (just wonder if it's a good thing to have to sync > bind/unbind operations waiting on async ones, but that's a different > topic). Yes, that's all correct. The page table allocation happens through nouveau_uvmm_vmm_get() which either allocates the corresponding page tables or increases the reference count, in case they already exist, accordingly. The call goes all the way through nvif into the nvkm layer (not the easiest to follow the call chain) and ends up in nvkm_vmm_ptes_get(). There are multiple reasons...

...he >>> VA space either (just wonder if it's a good thing to have to sync >>> bind/unbind operations waiting on async ones, but that's a different >>> topic). >> >> Yes, that's all correct. >> >> The page table allocation happens through nouveau_uvmm_vmm_get() which >> either allocates the corresponding page tables or increases the >> reference count, in case they already exist, accordingly. >> The call goes all the way through nvif into the nvkm layer (not the >> easiest to follow the call chain) and ends up in nvkm_vmm_ptes_ge...