__i915_gem_o...t_dirty_page(9)

💖 __i915_gem_o...t_dirty_page(9) 💖

okay so bestie, we're deep in the Kernel API Manual and this lil entry is literally about finding a target page by page offset. no cap, it's giving "small helper, big main character energy" ✨

---

✨ NAME ✨

__i915_gem_object_get_dirty_page — helper to find the target page with a page offset 🎀

---

🌸 SYNOPSIS 🌸

struct page * __i915_gem_object_get_dirty_page (struct
       drm_i915_gem_object *obj , pgoff_t n );

---

🦋 ARGUMENTS 🦋

• obj — i915 GEM buffer object 💅
• n — page offset 🌸

---

💜 DESCRIPTION 💜

okay so here's the tea: it works like i915_gem_object_get_page, but it marks the returned page dirty. that's the whole flex 🔥

Recommended to use wrapper macro: i915_gem_object_get_dirty_page — yes bestie, use the wrapper, it's right there 🫶

See also __i915_gem_object_page_iter_get_sg and __i915_gem_object_get_page 👀

---

⭐ RETURN ⭐

The target page pointer. periodt 💫

---

🌈 SEE ALSO 🌈

Kernel file: ./drivers/gpu/drm/i915/gem/i915_gem_object.h 🧚

• 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_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_pin_map(9)
• i915_gem_object_unpin_map(9)

---

and that's the page, bestie 💋 source/version vibes are ./drivers/gpu/drm/i915/gem, dated October 2026, and the footer title is __i915_gem_o...t_dirty_page(9) — mwah 🎀💖