drm_gpuvm_fo...a_range_safe(9)

💅 drm_gpuvm_for_each_va_range_safe — the safe range-walker (Kernel API Manual, section 9, bestie ✨)

okay so real talk: this is a kernel macro from the Kernel API Manual, section 9, and it's literally the "walk a slice of the VA tree without things exploding mid-loop" icon. let's get into it 🫶

---

✨ NAME ✨

drm_gpuvm_for_each_va_range_safe — safely iterate over a range of &drm_gpuvas

---

🌸 SYNOPSIS 🌸

drm_gpuvm_for_each_va_range_safe (va__ , next__ , gpuvm__ , start__ ,
end__ );

---

🎀 ARGUMENTS 🎀

• va__ — the drm_gpuva you assign to on every iteration step. this is your main character of the loop 👑
• next__ — another drm_gpuva that you keep around as temporary storage. it's the understudy, the safety net, the reason you can delete stuff mid-loop without crying 💀
• gpuvm__ — the drm_gpuvm you're walking over
• start__ — starting offset; the first gpuva will overlap this
• end__ — ending offset; the last gpuva will start before this (but it may overlap, no cap)

---

🦋 DESCRIPTION 🦋

so basically this iterator walks over all the drm_gpuvas in the drm_gpuvm that lie between start__ and end__. it's built similarly to list_for_each_safe, but plot twist — it uses the drm_gpuvm's internal interval tree to accelerate the search for the starting drm_gpuva, which is exactly why it's safe against removal of elements. you can yeet a gpuva out of the collection while you're iterating and it will not catch fire 🔥

⚠️ it assumes that end__ is within (or is the upper limit of) the drm_gpuvm. don't come for this macro if you hand it an end__ from somewhere else, fr fr 🙈

💀 also important: this iterator does not skip over the drm_gpuvm's kernel_alloc_node. so yeah, that node will show up in your loop. known behaviour, not a bug, iykyk.

---

🌈 SEE ALSO 🌈

Kernel file ./include/drm/drm_gpuvm.h, plus the whole friend group:

• enum drm_gpuva_flags(9)
• struct drm_gpuva(9)
• drm_gpuva_invalidate(9)
• drm_gpuva_invalidated(9)
• enum drm_gpuvm_flags(9)
• struct drm_gpuvm(9)
• drm_gpuvm_get(9)
• drm_gpuvm_resv_protected(9)
• drm_gpuvm_immediate_mode(9)
• drm_gpuvm_resv(9)
• drm_gpuvm_resv_obj(9)
• drm_gpuvm_is_extobj(9)
• drm_gpuvm_for_each_va_range(9)
• drm_gpuvm_for_each_va(9)
• drm_gpuvm_for_each_va_safe(9)
• struct drm_gpuvm_exec(9)
• drm_gpuvm_exec_unlock(9)
• drm_gpuvm_exec_resv_add_fence(9)
• drm_gpuvm_exec_validate(9)
• struct drm_gpuvm_bo(9)
• drm_gpuvm_bo_get(9)
• drm_gpuvm_bo_gem_evict(9)
• drm_gpuvm_bo_for_each_va(9)
• drm_gpuvm_bo_for_each_va_safe(9)
• enum drm_gpuva_op_type(9)
• struct drm_gpuva_op_map(9)
• struct drm_gpuva_op_unmap(9)
• struct drm_gpuva_op_remap(9)
• struct drm_gpuva_op_prefetch(9)
• struct drm_gpuva_op(9)
• struct drm_gpuva_ops(9)
• drm_gpuva_for_each_op(9)
• drm_gpuva_for_each_op_safe(9)
• drm_gpuva_for_each_op_from_reverse(9)
• drm_gpuva_for_each_op_reverse(9)
• drm_gpuva_first_op(9)
• drm_gpuva_last_op(9)
• drm_gpuva_prev_op(9)
• drm_gpuva_next_op(9)
• struct drm_gpuvm_map_req(9)
• struct drm_gpuvm_ops(9)
• drm_gpuva_op_remap_to_unmap_range(9)

---

and that's the whole vibe check bestie 💖 this page lives in ./include/drm, dated October 2026, and it's serving drm_gpuvm_fo...a_range_safe(9) realness. go read your interval trees, ily, mwah 🎀✨