xe_vma_user...e_invalidate(9)

💅 xe_vma_userptr_force_invalidate 💅

okay so bestie, welcome to the Kernel API Manual — yes this whole page lives in xe_vma_user...e_invalidate(9) land and it's lowkey a vibe. sit down, hydrate, and let's talk about forcing a userptr invalidation like the main character you are ✨

---

🌸 NAME 🌸

xe_vma_userptr_force_invalidate — force invalidate a userptr. that's it, that's the whole gig 💅

---

🎀 SYNOPSIS 🎀

void xe_vma_userptr_force_invalidate (struct xe_userptr_vma *uvma );

copy it exactly, don't be cute with the whitespace, iykyk 🫶

---

🦋 ARGUMENTS 🦋

• uvma — the userptr vma you're about to invalidate. bestie is the target. handle with love 💖

---

✨ DESCRIPTION ✨

so what does it actually do? it performs a forced userptr invalidation, and the reason is literally for testing purposes. no cap, that's the whole point — it's a testing hook, not your everyday production flow 🙈

ngl, "forced" is doing a lot of work in that sentence. it's intentional, it's for tests, so don't go treating it like a casual little helper in normal code. periodt 💀

---

👑 SEE ALSO 👑

• the kernel file, right here: ./drivers/gpu/drm/xe/xe_userptr.c — go read it, it's giving source of truth 📖
• xe_vma_userptr_check_repin(9)
• __xe_vm_userptr_needs_repin(9)
• xe_vm_userptr_check_repin(9)

like, the whole repin check squad 🧚 they all hang out together, go say hi 🌈

---

and that's the page!! mwah 💋 this little slice of the manual came from ./drivers/gpu/drm/xe, dated October 2026 — so when you're out here invalidating userptrs, remember who told you first 🎀🔥 ⭐