V9: Address capture support feedback from v8 V7: Rebased, minor cleanups as per review feedback V6: Rebased, minor fixes, add reserved fields to drm_i915_gem_vm_bind,Īdd new patch for async vm_unbind support V5: Render kernel-doc, use PIN_NOEVICT, limit vm_bind support to Replace vm->vm_bind_mode check with i915_gem_vm_is_vm_bind_mode() V4: Remove vm_unbind out fence uapi which is not supported yet, V3: Address review comments and other fixes * It is based on below VM_BIND design+uapi rfc. Legacy support like relocations etc., are removed. The new execbuf3 ioctl will not have any execlist support and all the The vm_bind mode only works with this new execbuf3 ioctl. This patch series support VM_BIND version 1, as described by the paramĪdd new execbuf3 ioctl (I915_GEM_EXECBUFFER3) which only works in To provide a list of all required mappings during each submission (as GPU submissions (execbuf calls) issued by the UMD, without user having Referred to as persistent mappings) will be persistent across multiple To the same physical pages of an object (aliasing).
Lionel.g.landwerlin, thomas.hellstrom, ld, jason,Īndi.shyti, daniel.vetter, christian.koenigĭRM_I915_GEM_VM_BIND/UNBIND ioctls allows UMD to bind/unbind GEMīuffer objects (BOs) or sections of a BOs at specified GPU virtualĪddresses on a specified address space (VM). Drm/i915/vm_bind: Add VM_BIND functionality All of help / color / mirror / Atom feed * drm/i915/vm_bind: Add VM_BIND functionality 7:15 ` Niranjana Vishwanathapura 0 siblings, 0 replies 81+ messages in threadįrom: Niranjana Vishwanathapura 7:15 UTC ( / raw)Ĭc: matthew.brost, paulo.r.zanoni, tvrtko.ursulin, jani.nikula,
0 kommentar(er)
