drm_mm_hole_node_end(9)

💅 drm_mm_hole_node_end(9) — like, the Kernel API Manual era 🎀

okay so bestie, we're deep in the kernel API manual rn and this one is a little helper function that tells you where a hole ends — yes, a hole, keep reading, it's about memory not vibes 💀

---

✨ NAME ✨

drm_mm_hole_node_end — literally computes the end of the hole that follows @node. that's it, that's the whole job 🫶

---

🌸 SYNOPSIS 🌸

u64 drm_mm_hole_node_end (const struct drm_mm_node *hole_node );

---

🦋 ARGUMENTS 🦋

• hole_node — a drm_mm_node that implicitly tracks the hole right after it. like it's not officially a "hole tracker" on paper but bestie it knows things 👀

---

💖 DESCRIPTION 💖

so this one is useful for driver-specific debug dumpers — that's its whole moment to shine ✨ otherwise? drivers should not be out here inspecting holes themselves, no cap. that's not your lane, stay in your lane 🚧

and before you even think about calling this, drivers must check first whether a hole indeed follows — how? by looking at drm_mm_hole_follows. vibe check your holes before you compute them, periodt 💅

fr fr do the drm_mm_hole_follows check first or you're just yolo-ing through memory 🙈

---

⭐ RETURN ⭐

the end of the subsequent hole. iconic. that's the answer, that's what you came for 👑

---

🌈 SEE ALSO 🌈

kernel file ./include/drm/drm_mm.h plus this whole cute little friend group 💜

• enum drm_mm_insert_mode(9)
• struct drm_mm_node(9)
• struct drm_mm(9)
• struct drm_mm_scan(9)
• drm_mm_node_allocated(9)
• drm_mm_initialized(9)
• drm_mm_hole_follows(9)
• drm_mm_hole_node_start(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)

---

and that's the page, bestie 🎀 sourced straight from ./include/drm and dated October 2026 — go forth and get that hole end, you absolute main character 💅✨🦋