xe_migrate_update_pgtables(9)

🌸 xe_migrate_update_pgtables(9) — the Kernel API Manual glow-up 🌸

Okay bestie, welcome to the page-table update pipeline, but make it cute ✨

---

🎀 NAME 🎀

• xe_migrate_update_pgtables — Pipelined page-table update 💅

---

✨ SYNOPSIS ✨

struct dma_fence * xe_migrate_update_pgtables (struct xe_migrate *m ,
struct xe_migrate_pt_update *pt_update );

---

💖 ARGUMENTS 💖

• m — the migrate context. Main character energy 🫶
• pt_update — PT update arguments. The receipts, basically 📝

---

🦋 DESCRIPTION 🦋

Okay so this literally performs a pipelined page-table update. The update descriptors are typically built under the same lock critical section as a call to this function — same-lock, same-critical-section vibes 🔒

If you’re using the default engine for the updates, they’ll be performed in the order they grab the job_mutex. If different engines are used, external synchronization is needed for overlapping updates to maintain page-table consistency. And just so we’re clear, “overlapping” here means the updates touch the same page-table — which might be a higher-level page-directory 👀

If no pipelining is needed, then updates may be performed by the cpu. Slay 💅

---

🫶 RETURN 🫶

A dma_fence that, when signaled, indicates the update completion. Signal = done, periodt 🔥

---

👑 SEE ALSO 👑

Kernel file: ./drivers/gpu/drm/xe/xe_migrate.c — and the whole friend group:

• 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_wait(9)
• xe_migrate_to_vram(9)
• xe_migrate_from_vram(9)
• xe_migrate_access_memory(9)
• xe_migrate_job_lock(9)
• xe_migrate_job_unlock(9)
• xe_migrate_job_lock_assert(9)

---

Footer tea, bestie: source/version field says ./drivers/gpu/drm/xe, date says October 2026, and the title is xe_migrate_update_pgtables(9). Bye, ily 💖✨