drm_mm_node_allocated(9)

💖 drm_mm_node_allocated — Kernel API Manual 💖

okay so bestie, welcome to the drm_mm_node_allocated page from the Kernel API Manual — it’s giving “tiny function, very important vibe check” ✨

---

💅 NAME 💅

drm_mm_node_allocated — checks whether a node is allocated 💖

✨ SYNOPSIS ✨

bool drm_mm_node_allocated (const struct drm_mm_node *node );

🎀 ARGUMENTS 🎀

• node — the drm_mm_node to check, bestie 🫶

🦋 DESCRIPTION 🦋

okay so drivers are required to clear a node before using it with the drm_mm range manager — no cap, that’s literally the rule 🙈

Drivers should use this helper for proper encapsulation of drm_mm internals. like, don’t go rummaging around in the internals yourself, bestie — use the helper, it’s the main character move 💅

🌸 RETURN 🌸

true if the node is allocated. that’s it, that’s the vibe check 🌈

🔥 SEE ALSO 🔥

Kernel file ./include/drm/drm_mm.h, plus this whole friend group:

• enum drm_mm_insert_mode(9)
• struct drm_mm_node(9)
• struct drm_mm(9)
• struct drm_mm_scan(9)
• drm_mm_initialized(9)
• drm_mm_hole_follows(9)
• drm_mm_hole_node_start(9)
• drm_mm_hole_node_end(9)
• drm_mm_nodes(9)
• drm_mm_for_each_node(9)
• drm_mm_for_each_node_safe(9)
• drm_mm_for_each_hole(9)
• drm_mm_insert_node_generic(9)
• drm_mm_insert_node(9)
• drm_mm_clean(9)
• drm_mm_for_each_node_in_range(9)
• drm_mm_scan_init(9)

---

mwah 💋 — that’s the whole page, bestie! source/version: ./include/drm, dated October 2026 — now go check those nodes 🫶✨