drm_mm_for_each_hole(9)

💖 NAME — drm_mm_for_each_hole(9) 💖

okay so welcome to the Kernel API Manual, bestie — this page is about drm_mm_for_each_hole, and it’s literally an iterator to walk over all holes. Slay. 💅✨

---

✨ SYNOPSIS ✨

drm_mm_for_each_hole (pos , mm , hole_start , hole_end );

---

🎀 ARGUMENTS 🎀

• pos — a drm_mm_node used internally to track progress 👀
• mm — the drm_mm allocator to walk 🚶‍♀️
• hole_start — a ulong variable to assign the hole start to on each iteration ⭐
• hole_end — a ulong variable to assign the hole end to on each iteration 🌈

---

🦋 DESCRIPTION 🦋

This iterator walks over all holes in the range allocator. It is implemented with list_for_each, so it is not save against removal of elements — yes, that’s the wording, bestie, and the vibe check is very much “do not expect removal-proof behavior.” 💀

entry is used internally and will not reflect a real drm_mm_node for the very first hole. Hence users of this iterator may not access it. No cap: do not go poking at entry. 🙈

Implementation Note: We need to inline list_for_each_entry in order to be able to set hole_start and hole_end on each iteration while keeping the macro sane.

---

🌈 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_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_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 bye bestie — this page is drm_mm_for_each_hole(9), coming at you from ./include/drm, October 2026. mwah 💋🫶