gpu_buddy_alloc_blocks(9)

🦋 NAME 🦋

gpu_buddy_alloc_blocks — allocate power-of-two blocks

okay so bestie, this is the page for gpu_buddy_alloc_blocks(9) from the Kernel API Manual, and it's literally about grabbing power-of-two blocks. iconic behavior fr fr 💅

---

✨ SYNOPSIS ✨

int gpu_buddy_alloc_blocks (struct gpu_buddy *mm , u64 start , u64 end ,
u64 size , u64 min_block_size , struct list_head *blocks , unsigned long
flags );

---

🎀 ARGUMENTS 🎀

• mm — the GPU buddy manager you're allocating from, your main character for this call 👑
• start — where the allowed range for this block starts
• end — where the allowed range for this block ends
• size — how big the allocation is, in bytes
• min_block_size — the alignment of the allocation
• blocks — output list head where the allocated blocks get added
• flags — the GPU_BUDDY_*_ALLOCATION flags

---

🌸 DESCRIPTION 🌸

alloc_range_bias gets called when there are range limitations — it traverses the tree and returns the desired block. yes, she's doing the whole tree walk, no cap 🌳✨

alloc_from_freetree gets called when no range restrictions are enforced — that one picks the block from the freetree. lowkey the simpler vibe 🍓

---

💖 RETURN 💖

0 on success, error code on failure. that's it, that's the tea 🫶

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/buddy.c — and these besties right here:

• gpu_buddy_assert(9)
• gpu_buddy_init(9)
• gpu_buddy_fini(9)
• gpu_buddy_reset_clear(9)
• gpu_buddy_free_block(9)
• gpu_buddy_allocated_addr_to_block(9)
• gpu_buddy_free_list(9)
• gpu_buddy_block_trim(9)
• gpu_buddy_block_print(9)
• gpu_buddy_print(9)

---

and that's the whole page!! source/version: ./drivers/gpu, date: October 2026 — mwah 💋✨