I915_PARAM_VM_BIND_VERSION(9)

💜 I915_PARAM_VM_BIND_VERSION 💜

okay bestie, this page is from the Kernel API Manual, and it's basically the vibe check for VM_BIND feature version supported. It tells you which version of VM_BIND is supported — for the param side of things, see typedef drm_i915_getparam_t param.

the defined versions of VM_BIND are giving:

• 0 — No VM_BIND support. that's it, that's the whole story 💀
• 1 — In VM_UNBIND calls, the UMD must specify the exact mappings created previously with VM_BIND, and the ioctl will not support unbinding multiple mappings or splitting them. Similarly, VM_BIND calls will not replace any existing mappings. strict queen behavior, no cap 👑
• 2 — The restrictions on unbinding partial or multiple mappings is lifted. Similarly, binding will replace any mappings in the given range. glow-up unlocked ✨

also peep struct drm_i915_gem_vm_bind and struct drm_i915_gem_vm_unbind — they're right there in the lore 🫶

🔎 SEE ALSO 🔎

• Kernel file ./Documentation/gpu/rfc/i915_vm_bind.h
• I915_VM_CREATE_FLAGS_USE_VM_BIND(9)
• struct drm_i915_gem_timeline_fence(9)
• struct drm_i915_gem_vm_bind(9)
• struct drm_i915_gem_vm_unbind(9)
• struct drm_i915_gem_execbuffer3(9)
• struct drm_i915_gem_create_ext_vm_private(9)

mwah 💋 this cute lil page lives under ./Documentation/gpu/rfc, dated October 2026, and it's literally I915_PARAM_VM_BIND_VERSION(9) — bye bestie 🦋