Lines Matching refs:VM
9 specified address space (VM). These mappings (also referred to as persistent
18 User has to opt-in for VM_BIND mode of binding for an address space (VM)
19 during VM creation time via I915_VM_CREATE_FLAGS_USE_VM_BIND extension.
38 submissions on that VM and will not be in the working set for currently running
43 A VM in VM_BIND mode will not support older execbuf mode of binding.
56 works with execbuf3 ioctl for submission. All BOs mapped on that VM (through
82 dma-resv fence list of all shared BOs mapped on the VM.
85 is private to a specified VM via I915_GEM_CREATE_EXT_VM_PRIVATE flag during
86 BO creation. Unlike Shared BOs, these VM private BOs can only be mapped on
87 the VM they are private to and can't be dma-buf exported.
88 All private BOs of a VM share the dma-resv object. Hence during each execbuf
91 w.r.t the number of VM private BOs.
115 dma-resv fence list of an object. Note that private BOs of a VM will all
121 3) Lock-C: Spinlock/s to protect some of the VM's lists like the list of
140 `Evictable page table allocations`_) and are maintained per VM and needs to
141 be pinned in memory when VM is made active (ie., upon an execbuf call with
142 that VM). So, bulk LRU movement of page table pages is also needed.
232 VM (difference here are that the page table pages will not have an i915_vma