xe_tlb_inval_range(9)

💖 NAME 💖

okay so bestie, this page is xe_tlb_inval_range(9) from the Kernel API Manual ✨ and it's all about xe_tlb_inval_range — Issue a TLB invalidation for an address range. no cap, that's the whole name vibe 💅

🌸 SYNOPSIS 🌸

the signature is literally giving:

int xe_tlb_inval_range (struct xe_tlb_inval *tlb_inval , struct
       xe_tlb_inval_fence *fence , u64 start , u64 end , u32 asid , struct
       drm_suballoc *prl_sa );

🎀 ARGUMENTS 🎀

• tlb_inval — TLB invalidation client, aka the lil' hookup for this call 💅
• fence — invalidation fence which will be signal on TLB invalidation completion 🔔
• start — start address, literally the beginning 📍
• end — end address, the finish line 🏁
• asid — address space id 🪪
• prl_sa — suballocation of page reclaim list if used, NULL indicates PPC flush 🧺

🦋 DESCRIPTION 🦋

okay so Issue a range based TLB invalidation if supported, and if not, fallback to a full TLB invalidation 🔥. Completion of TLB is asynchronous — yes bestie, it's doing its own thing 😭 — and the caller can use the invalidation fence to wait for completion. iykyk.

⭐ RETURN ⭐

Negative error code on error, 0 on success. that's the whole return vibe, periodt 💖

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/xe/xe_tlb_inval.c Xe TLB invalidation(9)
• tlb_inval_fini(9)
• xe_gt_tlb_inval_init_early(9)
• xe_tlb_inval_reset(9)
• xe_tlb_inval_reset_timeout(9)
• xe_tlb_inval_all(9)
• xe_tlb_inval_ggtt(9)
• xe_tlb_inval_vm(9)
• xe_tlb_inval_done_handler(9)
• xe_tlb_inval_fence_init(9)
• xe_tlb_inval_idle(9)
• xe_tlb_inval_batch_wait(9)
• xe_tlb_inval_range_tilemask_submit(9)

okay bestie, that's the whole page 💖 this one's from source/version ./drivers/gpu/drm/xe, dated October 2026, and the page is xe_tlb_inval_range(9). go off and invalidate responsibly 🫶✨