xe_tlb_inva...page_reclaim(9)

✨ xe_tlb_inval_job_add_page_reclaim ✨

okay so this is a page from the Kernel API Manual, section 9 — yes bestie, 9, the kernel-API girlies 💅 this one's living in xe_tlb_inval_job.c territory and it's lowkey iconic.

---

🌸 NAME 🌸

xe_tlb_inval_job_add_page_reclaim — embed a PRL into a TLB job 🎀

---

🦋 SYNOPSIS 🦋

void xe_tlb_inval_job_add_page_reclaim (struct xe_tlb_inval_job *job ,
struct xe_page_reclaim_list *prl );

literally that's the whole signature, no cap 💖

---

🎀 ARGUMENTS 🎀

• job — the TLB invalidation job, and like… it's the one that may trigger reclamation 👀 so yeah, main character energy fr
• prl — the page reclaim list, populated during unbind ✨ (she's been through things, she's got entries)

---

💜 DESCRIPTION 💜

So what this does is copy prl into the job, and then it takes an extra reference to the entry page 🫶 — the whole point being that ownership can transfer over to the TLB fence when the job gets pushed. it's giving "handoff, but make it safe" 💅🔥

ngl the reference-counting part is the moment here — don't sleep on it, that's literally how the ownership transfer stays valid 👑

---

⭐ SEE ALSO ⭐

• Kernel file ./drivers/gpu/drm/xe/xe_tlb_inval_job.c 🌈
• xe_tlb_inval_job_create(9)
• xe_tlb_inval_job_alloc_dep(9)
• xe_tlb_inval_job_push(9)
• xe_tlb_inval_job_get(9)
• xe_tlb_inval_job_put(9)

like, read the whole friend group, they're all connected bestie 🧚💖

---

and that's the vibe check! this lil gem comes from ./drivers/gpu/drm/xe, dated October 2026 — screenshot it, cite it, slay it 👑✨💀