i915_ttm_move(9)

💅 i915_ttm_move(9) — like, the whole page, bestie

okay so this is a page from the Kernel API Manual, and the star of the show is i915_ttm_move(9) ✨ — literally the TTM move callback that i915 uses. yes, that i915. the GPU one. we're in the kernel, bestie, act accordingly 🎀

---

🌸 NAME 🌸

i915_ttm_move — the TTM move callback that i915 uses. that's it, that's the tweet 💖

---

✨ SYNOPSIS ✨

int i915_ttm_move (struct ttm_buffer_object *bo , bool evict , struct
ttm_operation_ctx *ctx , struct ttm_resource *dst_mem , struct ttm_place
*hop );

look at her. five arguments, returns an int, absolutely iconic 👑

---

🦋 ARGUMENTS 🦋

• bo — the buffer object. the main character, honestly 🫶
• evict — a bool telling you whether this is an eviction. yes or no, no in-between 💀
• ctx — pointer to a struct ttm_operation_ctx that says how the waits should be performed if waiting. like, it's giving "instructions for the waiting part" 😭
• dst_mem — the destination ttm resource. where we're going 🚗✨
• hop — if we need multihop, this says what temporary memory type to move to. a little layover flight, iykyk ✈️

---

⭐ RETURN ⭐

0 if successful, negative error code otherwise 🌈

(so like... zero = slay, negative = something went sideways, check the code 💅)

---

🎀 SEE ALSO 🎀

• Kernel file ./drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c
• Selftest failure modes for failsafe migration:(9)
• i915_ttm_adjust_domains_after_move(9)
• i915_ttm_adjust_gem_after_move(9)
• i915_ttm_move_notify(9)
• struct i915_ttm_memcpy_arg(9)
• struct i915_ttm_memcpy_work(9)
• i915_gem_obj_copy_ttm(9)

---

lowkey a whole reading list. go read them, bestie, they're all connected 🧚‍♀️

---

okay that's the whole page, no cap 💜 and for the cute sign-off: this little beauty lives under ./drivers/gpu/drm/i915/gem, dated October 2026 — so like, future vibes, but the facts are timeless 🦋💖 see you in the next manpage, mwah 🫶✨