i915_gem_object_pin_map(9)

💖 NAME 💖

okay so bestie, this page is i915_gem_object_pin_map(9) from the Kernel API Manual, and it is literally the “return a contiguous mapping of the entire object” function. no cap. ✨

---

🦋 SYNOPSIS 🦋

void * i915_gem_object_pin_map (struct drm_i915_gem_object *obj , enum
       i915_map_type type );

---

🎀 ARGUMENTS 🎀

• obj — the object to map into kernel address space. main character energy, honestly.
• type — the type of mapping, used to select pgprot_t. it’s giving “which mapping flavor are we doing” vibes.

---

🌸 DESCRIPTION 🌸

okay so here’s the tea: i915_gem_object_pin_map calls i915_gem_object_pin_pages to prevent reaping of the object’s pages, and then returns a contiguous mapping of the backing storage into the kernel address space. slay. 💅 based on the type of mapping, the PTE will be set to either WriteBack or WriteCombine (via pgprot_t). lowkey important detail, bestie.

The caller is responsible for calling i915_gem_object_unpin_map when the mapping is no longer required. so do not forget to clean up — that’s your job, not the function’s. 🫶

It returns the pointer through which to access the mapped object, or an ERR_PTR on error. so check that return value, fr fr. 😭

---

🌈 SEE ALSO 🌈

Kernel file: ./drivers/gpu/drm/i915/gem/i915_gem_object.h — go peek, iykyk. 👑

• i915_gem_object_lookup_rcu(9)
• __i915_gem_object_page_iter_get_sg(9)
• i915_gem_object_page_iter_get_sg(9)
• __i915_gem_object_get_sg(9)
• i915_gem_object_get_sg(9)
• __i915_gem_object_get_sg_dma(9)
• i915_gem_object_get_sg_dma(9)
• __i915_gem_object_get_page(9)
• i915_gem_object_get_page(9)
• __i915_gem_object_get_dirty_page(9)
• i915_gem_object_get_dirty_page(9)
• __i915_gem_object_get_dma_address_len(9)
• i915_gem_object_get_dma_address_len(9)
• __i915_gem_object_get_dma_address(9)
• i915_gem_object_get_dma_address(9)
• i915_gem_object_unpin_map(9)

---

xoxo, source/version: ./drivers/gpu/drm/i915/gem · date: October 2026 · page: i915_gem_object_pin_map(9) 💋✨