xe_migrate_copy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, welcome to xe_migrate_copy(9) from the Kernel API Manual β€” it’s literally the function for copying content of TTM resources. that’s the whole assignment, and it ate. πŸ’…

✨ SYNOPSIS ✨

struct dma_fence * xe_migrate_copy (struct xe_migrate *m , struct xe_bo *src_bo , struct xe_bo *dst_bo , struct ttm_resource *src , struct ttm_resource *dst , bool copy_only_ccs );

πŸŽ€ ARGUMENTS πŸŽ€

  • m β€” the migration context. main character energy for this whole operation, ngl.
  • src_bo β€” the buffer object src is currently bound to. yes bestie, that one.
  • dst_bo β€” if you’re copying between resources created for the same bo, set this to the same value as src_bo. if you’re copying between buffer objects, set it to the buffer object dst is currently bound to. periodt.
  • src β€” the source TTM resource. the origin story.
  • dst β€” the dst TTM resource. the destination era.
  • copy_only_ccs β€” if true, copy only CCS metadata. that’s the vibe check right there.

πŸ¦‹ DESCRIPTION πŸ¦‹

so it copies the contents of src to dst: on flat CCS devices, the CCS metadata is copied as well if needed, or β€” if it’s not present β€” the CCS metadata of dst is cleared for security reasons. not me being dramatic, that’s just security doing security things. πŸ”₯

πŸ’« RETURN πŸ’«

pointer to a dma_fence representing the last copy batch, or an error pointer on failure. and if there is a failure, any copy operation started by the function call has been synced. so like, it cleans up its own situation. iconic. 🫢

πŸ‘‘ SEE ALSO πŸ‘‘


that’s the whole page, bestie 🫢 β€” source/version ./drivers/gpu/drm/xe, dated October 2026, page xe_migrate_copy(9). slay and bye πŸ’…

πŸ“¦ where this page comes from