xe_migrate_job_lock(9)

💅 xe_migrate_job_lock — NAME

okay bestie, welcome to the Kernel API Manual ✨ and today's main character is xe_migrate_job_lock — literally "Lock migrate job lock" 🎀 like yes that's the whole name and she's serving exactly what she says on the tin 🫶

---

🌸 SYNOPSIS

void xe_migrate_job_lock (struct xe_migrate *m , struct xe_exec_queue *q
);

ngl the synopsis is short and iconic, just how we like it 💖 note the space before those commas, that's canon, we don't touch it 🙈

---

✨ ARGUMENTS

• m — the migration context 🧚 that's your whole migration situation right there.
• q — the queue that's tied to whatever operation needs this lock 🔥 queue associated with the operation which requires a lock, periodt.

---

🔥 DESCRIPTION

okay so here's the vibe check 💅 it locks the migrate job lock if the queue is a migration queue 🎀

but if it is not a migration queue? then it asserts that the VM's dma-resv is held 😭 because user queues have their own locking, iykyk. no cap, that's the whole behaviour — lock in one case, assert in the other 🦋

lowkey important: this is an assertion, not a "please hold this for me" — the dma-resv has to already be held for the user-queue path 💀

---

🌈 SEE ALSO

• Kernel file ./drivers/gpu/drm/xe/xe_migrate.c ⭐
• struct xe_migrate(9)
• xe_migrate_alloc(9)
• xe_migrate_init(9)
• xe_migrate_copy(9)
• xe_migrate_resolve(9)
• xe_migrate_lrc(9)
• xe_migrate_ccs_rw_copy(9)
• xe_migrate_ccs_rw_copy_clear(9)
• xe_migrate_exec_queue(9)
• xe_migrate_vram_copy_chunk(9)
• xe_migrate_clear(9)
• xe_migrate_update_pgtables(9)
• xe_migrate_wait(9)
• xe_migrate_to_vram(9)
• xe_migrate_from_vram(9)
• xe_migrate_access_memory(9)
• xe_migrate_job_unlock(9)
• xe_migrate_job_lock_assert(9)

---

and that's the post 💌 this little masterpiece lives in ./drivers/gpu/drm/xe, dated October 2026 👑 go read the whole migrate family, they ate fr fr 🍓✨