i915_gem_obj_copy_ttm(9)

okay bestie, this is i915_gem_obj_copy_ttm(9) from the Kernel API Manual — literally the page about copying the contents of one ttm-based gem object to another, and it is giving very specific kernel business 💅✨

🌸 NAME 🌸

i915_gem_obj_copy_ttm — copy the contents of one ttm-based gem object to another. that's the assignment, and it ate 💖

🦋 SYNOPSIS 🦋

int i915_gem_obj_copy_ttm (struct drm_i915_gem_object *dst , struct
       drm_i915_gem_object *src , bool allow_accel , bool intr );

🎀 ARGUMENTS 🎀

• dst — the destination object, aka the one receiving the copy, main character energy 🫶
• src — the source object, aka the one the copy comes from, we love a reliable source ✨
• allow_accel — Allow using the blitter. Otherwise TTM memcpy is used. bestie, it's giving “blitter if allowed, TTM memcpy otherwise” 🔥
• intr — Whether to perform waits interruptible:</se> yes, that colon is literally part of the original, and we respect it 🙈

💜 NOTE 💜

The caller is responsible for assuring that the underlying TTM objects are populated if needed and locked. that's on you, bestie — no cap, don't skip the prep work 😭

⭐ RETURN ⭐

• Zero on success.
• Negative error code on error.
• If intr == true, then it may return -ERESTARTSYS or -EINTR. so if you asked for interruptible waits, those are the plot twists 💀

🌈 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_ttm_move(9)

and that's the page, bestie 🎀 source/version: ./drivers/gpu/drm/i915/gem, date: October 2026, manual: i915_gem_obj_copy_ttm(9). slay, bye 💋✨