Hi Niranjana, On Tue, Sep 27, 2022 at 11:19:10PM -0700, Niranjana Vishwanathapura wrote: > Do not use i915_vma activeness tracking for persistent vmas. > > As persistent vmas are part of working set for each execbuf > submission on that address space (VM), a persistent vma is > active if the VM active. As vm->root_obj->base.resv will be > updated for each submission on that VM, it correctly > represent whether the VM is active or not. > > Add i915_vm_is_active() and i915_vm_sync() functions based > on vm->root_obj->base.resv with DMA_RESV_USAGE_BOOKKEEP > usage. dma-resv fence list will be updated with this usage > during each submission with this VM in the new execbuf3 > ioctl path. > > Update i915_vma_is_active(), i915_vma_sync() and the > __i915_vma_unbind_async() functions to properly handle > persistent vmas. > > Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@xxxxxxxxx> Reviewed-by: Andi Shyti <andi.shyti@xxxxxxxxxxxxxxx> Andi
