xe_bo_willneed_get_locked(9)

✨ xe_bo_willneed_get_locked(9) ✨

okay so bestie, this one's from the Linux kernel API manual (section 9, the kernel-Doc zone 🫶), and it's literally all about grabbing a WILLNEED holder on a BO. tiny function, big main-character energy. let's get into it 💅

---

🌸 SYNOPSIS 🌸

void xe_bo_willneed_get_locked (struct xe_bo *bo );

no return value, no drama, it just does the thing ✨

---

🎀 ARGUMENTS 🎀

• bo — buffer object. that's it. that's the whole argument list. she's minimal 💖

---

🔥 DESCRIPTION 🔥

okay so here's the tea ☕ — this function increments willneed_count, and on a 0->1 transition it promotes the BO from DONTNEED to WILLNEED. glow-up behavior fr fr ✨

and PURGED? that state is terminal — it is never modified. not by this function, not by anyone. she's locked in, periodt 💀👑

⚠️ important bestie: the caller must hold the BO's dma-resv lock. this is not optional, this is not a suggestion, do not skip it 🙈

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/xe/xe_bo.h enum
• xe_madv_purgeable_state(9)
• xe_bo_is_purged(9)
• xe_bo_madv_is_dontneed(9)
• xe_bo_willneed_put_locked(9)
• xe_bo_vma_count_inc_locked(9)
• xe_bo_vma_count_dec_locked(9)
• xe_bo_size(9)
• xe_bo_has_valid_ccs_bb(9)
• xe_bo_put_deferred(9)
• xe_bo_put_async(9)
• xe_bo_sg_is_contiguous(9)
• struct xe_bo_shrink_flags(9)
• xe_bo_is_mem_type(9)

like a whole friend group of BO helpers, and they all ate 💅✨

---

and that's the whole page, bestie 🫶 this lil guy lives in ./drivers/gpu/drm/xe, the manual's dated October 2026, and it's serving xe_bo_willneed_get_locked(9) realness from the Linux kernel API manual. go forth and hold your locks 🎀💖