xe_pt_update_ops_run(9)

✨ xe_pt_update_ops_run(9) ✨

okay so real talk, this is a page from the Kernel API Manual and it's about a function called xe_pt_update_ops_run — say that five times fast, I dare you 💀. It's giving "the final boss of page-table updates" energy and honestly? obsessed.

---

🌸 NAME 🌸

xe_pt_update_ops_run — Run PT update operations

---

🎀 SYNOPSIS 🎀

struct dma_fence * xe_pt_update_ops_run (struct xe_tile *tile , struct
xe_vma_ops *vops );

---

💅 ARGUMENTS 💅

• tile — the Tile of PT update operations. like, which tile we're doing this whole thing on, bestie 🧚
• vops — the VMA operations. (the manpage fr says "VMA operationa" — iconic typo, no cap, but you get it: VMA ops 💖)

---

🌈 DESCRIPTION 🌈

So what does it do? It runs the PT update operations. And before you're like "girl that's circular" — no, listen 👑

This is the whole bundle: it commits internal PT state changes, it creates the job for the PT update operations (specifically for leaf insertion / removal, iykyk), and it installs the job fence in various places. Three vibes, one function. main character energy fr fr ✨

---

🔥 RETURN 🔥

• a fence on success 🎉
• a negative ERR_PTR on error 😭

that's it. that's the whole contract. no grey area, we love a clear return value 💜

---

🦋 SEE ALSO 🦋

okay bestie, buckle up, the friend group is LARGE and everyone's here:

• Kernel file ./drivers/gpu/drm/xe/xe_pt.c
• xe_pt_create(9)
• xe_pt_populate_empty(9)
• xe_pt_shift(9)
• xe_pt_destroy(9)
• xe_pt_clear(9)
• Pagetable building(9)
• struct xe_pt_stage_bind_walk(9)
• xe_pt_stage_bind(9)
• xe_pt_nonshared_offsets(9)
• xe_pt_zap_ptes(9)
• xe_pt_zap_ptes_range(9)
• xe_pt_stage_unbind(9)
• xe_pt_update_ops_prepare(9)
• xe_pt_update_ops_fini(9)
• xe_pt_update_ops_abort(9)

---

and that's the page!! 💖 shoutout to ./drivers/gpu/drm/xe for being the source, and to October 2026 for the date stamp — future girlies will be reading this and slaying just as hard 🫶🌸 periodt.