xe_sa_bo_alloc(9)

✨ xe_sa_bo_alloc ✨

okay so this is a page from the Kernel API Manual — section 9 — and the function is literally called xe_sa_bo_alloc, bestie. it's giving "tiny but crucial" energy 💅

---

🌸 NAME 🌸

xe_sa_bo_alloc — allocate an uninitialized suballoc object 🎀

🦋 SYNOPSIS 🦋

struct drm_suballoc * xe_sa_bo_alloc (gfp_t gfp );

like, that's the whole vibe. one argument, one pointer back. no cap 🫶

💜 ARGUMENTS 💜

• gfp — the gfp flags, and these are the ones used for the memory allocation itself. yes bestie, that's your whole say in how the memory gets grabbed 🔥

🌈 DESCRIPTION 🌈

so what it does is: allocate memory for an uninitialized suballoc object. that's it, that's the whole job ✨

the intended usage (pay attention, this is the main character part 👑) is to allocate the memory for the suballoc object outside of a reclaim tainted context, and then have it be initialized at a later time, in a reclaim tainted context. so: allocation now, init later 🧚

ngl the whole point is doing the alloc-y bit where it's safe and the init-y bit later — that ordering is the lore, don't skip it 🙈

⭐ RETURN ⭐

it hands you back a new uninitialized suballoc object, or ERR_PTR(-ENOMEM) if the allocation didn't work out 😭 (yes, check it. fr fr.)

🌸 SEE ALSO 🌸

• Kernel file ./drivers/gpu/drm/xe/xe_sa.c — __xe_sa_bo_manager_init(9), xe_sa_bo_swap_shadow(9), xe_sa_bo_sync_shadow(9), __xe_sa_bo_new(9), xe_sa_bo_init(9), xe_sa_bo_flush_write(9), xe_sa_bo_sync_read(9)

like the whole squad is linked above, go read them too, iykyk 💖

---

🍓 that's the page!! it lives over in ./drivers/gpu/drm/xe, and this legendary little manual was dated October 2026 — slay, iconic, periodt. go forth and suballoc responsibly bestie 💅✨