drm_mm_hole_node_start(9)

✨ drm_mm_hole_node_start(9) ✨

okay so bestie, welcome to the drm_mm_hole_node_start page from the Kernel API Manual 💖 this one's a lil function but she's got main character energy in the debug-dumper department. let's get into it 🎀

---

🌸 NAME 🌸

drm_mm_hole_node_start — literally computes the start of the hole following @node 🕳️✨

---

🦋 SYNOPSIS 🦋

u64 drm_mm_hole_node_start (const struct drm_mm_node *hole_node );

---

🎀 ARGUMENTS 🎀

• hole_node — a drm_mm_node which implicitly tracks the following hole 👀 (yes, implicitly, she's not gonna spell it out for you, that's the whole vibe)

---

💅 DESCRIPTION 💅

so like, this one is useful for driver-specific debug dumpers, periodt. that's her moment 💖

otherwise? drivers should not go poking at holes themselves, ngl, that's not your business bestie 🙈

drivers must check first whether a hole indeed follows by looking at drm_mm_hole_follows — like, do the vibe check before you commit, fr fr ⭐

---

🔥 RETURN 🔥

Start of the subsequent hole 🕳️➡️🕳️ slay.

---

🌈 SEE ALSO 🌈

• Kernel file ./include/drm/drm_mm.h
• 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_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)

---

okay that's the whole page bestie, you ate that 🫶 this lil drop came straight outta ./include/drm, dated October 2026, and it's the drm_mm_hole_node_start(9) era — iykyk 💜✨ 🧚