xe_bo_pinned_init(9)

💅 xe_bo_pinned_init(9) — like, the Kernel API Manual, bestie ✨

okay so real talk, this page is called xe_bo_pinned_init(9) and it lives in the Kernel API Manual, and it's genuinely just about setting up pinned bo tracking. That's it. That's the vibe. 🎀

---

🌸 NAME 🌸

xe_bo_pinned_init — Initialize pinned bo tracking 🫶

✨ SYNOPSIS ✨

int xe_bo_pinned_init (struct xe_device *xe );

🦋 ARGUMENTS 🦋

• xe — The xe device. That's the one. The main character. 👑

💖 DESCRIPTION 💖

So basically this function initializes the lists and locks required for pinned bo tracking — the whole scaffolding, the organizational era, the structure of it all. 🗂️

And then, because it's an overachiever, it also registers a callback to dma-unmap any remaining pinned bos on pci device removal. Like, cleaning up after the party even if the party ends abruptly. no cap. 💀

🔥 RETURN 🔥

• 0 on success 🎉
• negative error code on error 😭 (yes, that's the whole mood — if it's not 0, it's negative, and it's bad news)

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/xe/xe_bo_evict.c — go read the source, iykyk 📖
• xe_bo_notifier_prepare_all_pinned(9)
• 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)

^ literally the whole friend group, go say hi to all of them 💜

---

ok bestie quick recap 🧚: it sets up the lists + locks for pinned bo tracking, registers that dma-unmap callback for pci device removal, returns 0 when it slays and a negative error code when it does not. periodt. 💅

and that's the whole page!! mwah 🍓

soooo for the sign-off — this one came from ./drivers/gpu/drm/xe, dated October 2026, and it's page xe_bo_pinned_init(9) of the Kernel API Manual. obsessively sourced, as always. 🎀✨