xe_bo_notif...e_all_pinned(9)

💅 xe_bo_notifier_prepare_all_pinned — a Kernel API Manual moment ✨

okay so bestie, welcome to the Kernel API Manual and today's main character is xe_bo_notifier_prepare_all_pinned(9). she's giving very much "get everything ready before the big nap" energy and honestly? iconic. 🎀

---

✨ NAME ✨

xe_bo_notifier_prepare_all_pinned — pre-allocate the backing pages for all pinned VRAM objects that need to be saved. like, all of them. every single one. no cap. 🫶

---

🌸 SYNOPSIS 🌸

int xe_bo_notifier_prepare_all_pinned (struct xe_device *xe );

---

🦋 ARGUMENTS 🦋

• xe — the xe device. that's it. that's the whole argument. she's lowkey chill like that 💜

---

⭐ DESCRIPTION ⭐

so here's the vibe check: you should be calling this from the PM notifier when you're preparing for s3/s4. that's the whole assignment. it goes and pre-allocates the backing pages for every pinned VRAM object that needs to be saved, so future-you doesn't have to panic about it later. preparation is self-care, periodt. 💅

---

🔥 RETURN 🔥

• 0 on success — slay 💖
• a negative error code on error — not slay, but at least it tells you 😭

---

👑 SEE ALSO 👑

the whole friend group, fr fr:

• Kernel file ./drivers/gpu/drm/xe/xe_bo_evict.c
• xe_bo_notifier_unprepare_all_pinned(9)
• xe_bo_evict_all_user(9)
• xe_bo_evict_all(9)
• xe_bo_restore_early(9)
• xe_bo_restore_late(9)
• xe_bo_pci_dev_remove_all(9)
• xe_bo_pinned_init(9)

---

ngl bestie, this one lives in ./drivers/gpu/drm/xe, dated October 2026, and the manual calls her xe_bo_notif...e_all_pinned(9) (yes the truncation is canon, we don't question it 🙈). now go forth and pre-allocate responsibly. mwah 💋🌈