drm_mm_print(9)

💅 drm_mm_print(9) — the kernel API manual, bestie edition

okay so this is a page from the Kernel API Manual, and we're talking about drm_mm_print(9) — the little function that spills all the tea about your allocator's current state. Let's get into it 🫶

---

✨ NAME ✨

drm_mm_print — print allocator state

like, it literally prints the state of the allocator. no notes. iconic behaviour honestly 💅

---

🌸 SYNOPSIS 🌸

void drm_mm_print (const struct drm_mm *mm , struct drm_printer *p );

void function, two args, zero drama. she takes a pointer to the allocator and a pointer to a printer and that's the whole vibe ✨

---

🎀 ARGUMENTS 🎀

• mm — the drm_mm allocator you want to print, bestie. this is the one spilling its guts 💖
• p — the DRM printer to use. she's the messenger, the output destination, the main character of the printing arc 🦋

---

👑 SEE ALSO 👑

okay so if you're going down the rabbit hole (and you know you are), here's the whole friend group 🫶:

• Kernel file ./drivers/gpu/drm/drm_mm.c Overview(9)
• DECLARE_NEXT_HOLE_ADDR(9)
• drm_mm_reserve_node(9)
• drm_mm_insert_node_in_range(9)
• drm_mm_remove_node(9)
• lru scan roster(9)
• drm_mm_scan_init_with_range(9)
• drm_mm_scan_add_block(9)
• drm_mm_scan_remove_block(9)
• drm_mm_scan_color_evict(9)
• drm_mm_init(9)
• drm_mm_takedown(9)

literally a whole squad. go read them, iykyk 💜

---

and that's the page!! sourced from ./drivers/gpu/drm, dated October 2026, and the header says drm_mm_print(9) obviously, because she's the moment ⭐

anyway ily, go print your allocator state responsibly, and remember: no cap, you got this 🧚💖