drm_gpusvm_...otifier_safe(9)
β¨ NAME β¨
drm_gpusvm_for_each_notifier_safe β safely iterate over GPU SVM notifiers in a gpusvm. This little icon lives in the Kernel API Manual, section 9, and it's here to help you loop without the chaos.
πΈ SYNOPSIS πΈ
drm_gpusvm_for_each_notifier_safe (notifier__ , next__ , gpusvm__ , start__ , end__ );
π ARGUMENTS π
notifier__β your iterator variable for the notifiers.next__β iterator variable for the notifiers' temporary storage.gpusvm__β pointer to the GPU SVM notifier.start__β start address of the notifier.end__β end address of the notifier.
π DESCRIPTION π
This macro is used to iterate over GPU SVM notifiers in a gpusvm while removing notifiers from it. So yes bestie, it's giving walk-the-list-while-stuff-is-getting-removed energy, and the _safe in the name is doing exactly what you think it's doing. π«Ά
π¦ SEE ALSO π¦
Kernel file ./include/drm/drm_gpusvm.h is the home base, and here's the full friend group:
struct drm_gpusvm_ops(9)struct drm_gpusvm_notifier(9)struct drm_gpusvm_pages_flags(9)struct drm_gpusvm_pages(9)struct drm_gpusvm_range_flags(9)struct drm_gpusvm_range(9)struct drm_gpusvm(9)struct drm_gpusvm_ctx(9)drm_gpusvm_init_pages(9)enum drm_gpusvm_scan_result(9)drm_gpusvm_driver_set_lock(9)drm_gpusvm_notifier_lock(9)drm_gpusvm_notifier_unlock(9)drm_gpusvm_range_start(9)drm_gpusvm_range_end(9)drm_gpusvm_range_size(9)drm_gpusvm_notifier_start(9)drm_gpusvm_notifier_end(9)drm_gpusvm_notifier_size(9)__drm_gpusvm_range_next(9)drm_gpusvm_for_each_range(9)drm_gpusvm_for_each_range_safe(9)__drm_gpusvm_notifier_next(9)drm_gpusvm_for_each_notifier(9)
okay that's the whole page, bestie π source spot: ./include/drm; dated October 2026; page name: drm_gpusvm_...otifier_safe(9).
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms