svm_range_check_vm(9)

💅 svm_range_check_vm(9) 💅

okay bestie, welcome to the Kernel API Manual — today's main character is svm_range_check_vm(9), and she is literally here to check if a virtual address range is already mapped. no cap. ✨

---

✨ NAME ✨

svm_range_check_vm — check if virtual address range mapped already

---

🌸 SYNOPSIS 🌸

int svm_range_check_vm (struct kfd_process *p , uint64_t start ,
       uint64_t last , uint64_t *bo_s , uint64_t *bo_l );

---

🎀 ARGUMENTS 🎀

• p — current kfd_process
• start — range start address, in pages
• last — range last address, in pages
• bo_s — mapping start address in pages if address range already mapped
• bo_l — mapping last address in pages if address range already mapped

---

🦋 DESCRIPTION 🦋

okay so the whole purpose here is to avoid virtual address ranges that are already allocated by the kfd_ioctl_alloc_memory_of_gpu ioctl. lowkey important. It literally looks for each pdd in the kfd_process. 👑

Return vibe check: returns 0 — OK, if the range is not mapped. Otherwise error code:

• -EADDRINUSE — if address is mapped already by kfd_ioctl_alloc_memory_of_gpu
• -ERESTARTSYS — A wait for the buffer to become unreserved was interrupted by a signal. Release all buffer reservations and return to user-space.

---

🧚 CONTEXT 🧚

Process context. periodt. 💅

---

🌈 SEE ALSO 🌈

Kernel file: ./drivers/gpu/drm/amd/amdkfd/kfd_svm.c

the whole SEE ALSO squad is:

• svm_range_unlink(9)
• svm_range_add_to_svms(9)
• svm_range_debug_dump(9)
• svm_range_split_adjust(9)
• svm_range_split(9)
• svm_range_list_lock_and_flush_work(9)
• svm_range_evict(9)
• svm_range_add(9)
• svm_range_cpu_invalidate_pagetables(9)
• svm_range_from_addr(9)
• svm_range_is_valid(9)
• svm_range_best_prefetch_location(9)

---

mwah 💋 this little page comes from the source/version line ./drivers/gpu/drm/amd/amdkfd and is dated October 2026; it's the svm_range_check_vm(9) entry. bye bestie, go check those ranges 🫶