i915_ttm_buddy_man_reserve(9)

💖 NAME 💖

Okay so this is the i915_ttm_buddy_man_reserve(9) page from the Kernel API Manual, and its whole main-character job is literally to reserve address range. That’s the vibe. 🎀

✨ SYNOPSIS ✨

int i915_ttm_buddy_man_reserve (struct ttm_resource_manager *man , u64
start , u64 size );

🫶 ARGUMENTS 🫶

• man — the buddy allocator ttm manager. Like, the manager for the buddy allocator, bestie. 💅
• start — the offset in bytes, where the region start is assumed to be zero. Yes, zero. We’ll get to it. 👀
• size — the size in bytes. The amount of bytes. The size of the thing. 🍓

🌸 DESCRIPTION 🌸

Important vibe check: the starting address for the region is always assumed to be zero. No cap. So don’t come in here with some other starting address and expect it to slay — the page literally says the region start is assumed to be zero. 🦋

🔥 RETURN 🔥

• 0 on success — slay. ✅
• negative error code on failure — not the vibe, but that’s what you get. 😭

🌈 SEE ALSO 🌈

Kernel file:

./drivers/gpu/drm/i915/i915_ttm_buddy_manager.c

And these iconic siblings, fr fr:

• i915_ttm_buddy_man_init(9)
• i915_ttm_buddy_man_fini(9)
• i915_ttm_buddy_man_visible_size(9)
• i915_ttm_buddy_man_avail(9)

Signed with sparkles by the i915_ttm_buddy_man_reserve(9) page, coming at you from ./drivers/gpu/drm/i915, dated October 2026 — periodt. 💜