STRUCT XE_MADVISE_DETAILS(9)

💅 struct xe_madvise_details(9) 💅

okay so bestie, welcome to the Kernel API Manual — we're talking about struct xe_madvise_details today and honestly? she's a little supporting character with main character energy. let's get into it 🎀

---

✨ NAME ✨

struct xe_madvise_details — the argument that gets passed to madvise_funcs, and yes she eats every time 🫶

---

🌸 SYNOPSIS 🌸

struct xe_madvise_details {
    struct drm_pagemap *dpagemap;
    bool has_purged_bo;
    u64 retained_ptr;
 };

---

🦋 Members 🦋

• dpagemap — a reference-counted pointer to a struct drm_pagemap. that's it, that's the whole vibe. refcounted means somebody's keeping score, iykyk 💅
• has_purged_bo — tracks whether any BO got purged. it's giving "was anybody lost in the purge" energy, and it exists for the purgeable state. lowkey important 🌈
• retained_ptr — a user pointer pointing at the retained value. also for the purgeable state. she holds onto things, ngl 🧚

---

💖 Description 💖

so here's the tea ☕ — the madvise IOCTL handler might have more to say than just the user-space args. like, sometimes there's extra info that needs to get passed into the madvise_func that handles the specific madvise type. and that's literally what struct xe_madvise_details is for 🫶

use a struct_xe_madvise_details for that extra info, and extend the struct whenever you need to. she's flexible, she grows with you, no cap 💀✨

---

🔥 SEE ALSO 🔥

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

go read those, bestie, they're all in the same friend group 👑

---

reminder bestie: this whole thing lives in ./drivers/gpu/drm/xe and the version stamp says October 2026 — so like, mark your calendar, she's from the future 💫

okay that's the whole page, mwah 💋 struct xe_madvise_details(9) out 🎀💜