madvise_purgeable(9)

okay so bestie, welcome to madvise_purgeable(9) — that’s the manual name, and we’re in the Kernel API Manual 💖 buckle up, this one’s short but it’s got lore.

✨ NAME ✨

madvise_purgeable — handle purgeable buffer object advice. that’s the whole name sitch, and yes it’s giving kernel-internals main character energy 👑

🦋 SYNOPSIS 🦋

okay here’s the exact signature, copy it like your life depends on it:

void madvise_purgeable (struct xe_device *xe , struct xe_vm *vm , struct
       xe_vma **vmas , int num_vmas , struct drm_xe_madvise *op , struct
       xe_madvise_details *details );

no cap, that’s the whole call 💅

🎀 ARGUMENTS 🎀

• xe — XE device. literally the device, bestie 🫶
• vm — VM. she’s mysterious but essential 💜
• vmas — Array of VMAs. yes, an array, plural, iconic ✨
• num_vmas — Number of VMAs. the count, the vibe check 🔢
• op — Madvise operation. the operation in question 💅
• details — Madvise details for return values. where the receipts go 🧾

🔥 DESCRIPTION 🔥

okay so this function handles the DONTNEED/WILLNEED/PURGED states — those three, exactly, no extras, periodt ✨

It also tracks if any BO was purged in details->has_purged_bo for later copy to userspace. that’s the whole tracking vibe: if a BO got purged, it’s noted there so it can be copied to userspace later 💖

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/xe/xe_vm_madvise.c
• struct xe_madvise_details(9)
• madvise_range_needs_invalidation(9)
• xe_vm_madvise_ioctl(9)

go read those too, bestie, it’s giving linked-list of lore 🦋

mwah 💋 this lil page is from ./drivers/gpu/drm/xe and it’s dated October 2026 — slay, bye! 🌸