i915_ttm_adj...m_after_move(9)

💅 i915_ttm_adj...m_after_move(9) 💅

okay so you're looking at the Kernel API Manual bestie, and this is the page for i915_ttm_adjust_gem_after_move — yes the filename up top got chopped to i915_ttm_adj...m_after_move(9) and no we're not fixing it, it's giving truncated-but-iconic. 🎀

---

✨ NAME ✨

i915_ttm_adjust_gem_after_move — Adjust the GEM state after a TTM move. that's the whole gig. no cap. 💖

---

🌸 SYNOPSIS 🌸

void i915_ttm_adjust_gem_after_move (struct drm_i915_gem_object *obj );

void function, one arg, in and out. slay. ✨

---

🦋 ARGUMENTS 🦋

• obj — The gem object. that's it, that's the one (1) parameter, and it's the gem object you're adjusting. 🫶

---

💅 DESCRIPTION 💅

so after a TTM move happens, this function goes in and fixes up the GEM object's region, its mem_flags, and its cache coherency. that's the whole vibe check: region ✅, mem_flags ✅, cache coherency ✅.

like, the object just got moved around by TTM and now it needs its GEM-side state to match reality. this is the "bestie let me fix your hair before you go out" of functions. literally. 🔥

---

👑 SEE ALSO 👑

• Kernel file ./drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c — the whole source vibe lives here, iykyk 👀
• Selftest failure modes for failsafe migration:(9)
• i915_ttm_adjust_domains_after_move(9) — the domains sibling, obsessed
• i915_ttm_move_notify(9)
• struct i915_ttm_memcpy_arg(9)
• struct i915_ttm_memcpy_work(9)
• i915_ttm_move(9)
• i915_gem_obj_copy_ttm(9)

go read them all, they're all in the group chat 💜

---

and that's the page!! 🌈 this little gem came from the source path ./drivers/gpu/drm/i915/gem, dated October 2026 — mwah, see you in the next move 🍓💖✨