gpu_buddy_print(9)

💅 gpu_buddy_print(9) — from the Kernel API Manual, bestie 🎀

okay so picture this: it's giving kernel API manual, it's giving GPU allocator lore, and honestly? we're obsessed. this page is about gpu_buddy_print, and yes it's exactly what it sounds like — it prints the allocator state. no cap, that's the whole vibe. let's get into it ✨

---

🌸 NAME 🌸

gpu_buddy_print — print allocator state

like literally, it prints the state of the allocator. main character energy for a debugging function tbh 🫶

---

✨ SYNOPSIS ✨

void gpu_buddy_print (struct gpu_buddy *mm );

that's it. that's the whole call. returns void, so nothing comes back to you — the output goes wherever print goes. lowkey iconic 💅

---

🦋 ARGUMENTS 🦋

• mm — the GPU buddy manager 💖 (yes, that's the actual parameter name, and yes it stands for the manager struct, we love a good abbreviation)

---

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/gpu/buddy.c, and it's surrounded by a whole friend group of related calls — go say hi to all of them:

• 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_alloc_blocks(9)
• gpu_buddy_block_print(9)

iykyk, the buddy allocator fam is thriving 🧚

---

ngl bestie, this page is short and sweet — no flags, no exit statuses, no environment variables, no warnings, no bug notes. just one function, one argument, and a whole lot of cross-references. sometimes less is more, periodt 💀

---

and that's the tea 🍓 this one came from the kernel source tree at ./drivers/gpu, dated October 2026, and it's the gpu_buddy_print(9) page — slay, go print some allocator state, bestie 💜🔥