drm_gpusvm_range_evict(9)

💅 drm_gpusvm_range_evict(9) — Kernel API Manual, bestie edition

okay so real talk, this is drm_gpusvm_range_evict, straight out of the kernel API manual, and it's lowkey one of the most straightforward little functions you'll ever meet. no cap. let's get into it 🫶

---

✨ NAME ✨

drm_gpusvm_range_evict — Evict GPU SVM range

like... that's it. that's the whole job. she evicts. she's an evictor. iconic behavior honestly 👑

---

🌸 SYNOPSIS 🌸

int drm_gpusvm_range_evict (struct drm_gpusvm *gpusvm , struct
drm_gpusvm_range *range );

look at her. two params, returns an int. clean. minimal. the way that she doesn't overcomplicate things?? we stan 💖

---

🎀 ARGUMENTS 🎀

• gpusvm — Pointer to the GPU SVM structure. that's the big-picture one, the main character of the whole GPU SVM situation 🧚
• range — Pointer to the GPU SVM range to be removed. yes bestie, the one getting evicted. it's giving "your subscription has ended" energy 😭

---

🦋 DESCRIPTION 🦋

This function evicts the specified GPU SVM range. that's the tea, that's the whole plot 🍓 she takes the range you hand her and she evicts it. no extra steps, no surprise plot twists, fr fr.

---

⭐ RETURN ⭐

• 0 on success 🎉 slay
• a negative error code on failure 💀 not slay, but at least you know

---

🔥 SEE ALSO 🔥

okay this is the part where I hold your hand and walk you through the whole friend group, because this function does NOT exist in a vacuum:

Kernel file ./drivers/gpu/drm/drm_gpusvm.c Overview(9), Locking(9), Partial Unmapping of Ranges(9), Examples(9), npages_in_range(9), drm_gpusvm_notifier_find(9), drm_gpusvm_range_find(9), drm_gpusvm_notifier_invalidate(9), drm_gpusvm_init(9), to_drm_gpusvm_notifier(9), drm_gpusvm_notifier_insert(9), drm_gpusvm_notifier_remove(9), drm_gpusvm_fini(9), drm_gpusvm_notifier_alloc(9), drm_gpusvm_notifier_free(9), to_drm_gpusvm_range(9), drm_gpusvm_range_insert(9), __drm_gpusvm_range_remove(9), drm_gpusvm_range_alloc(9), drm_gpusvm_hmm_pfn_to_order(9), drm_gpusvm_check_pages(9), drm_gpusvm_scan_mm(9), drm_gpusvm_range_chunk_size(9), drm_gpusvm_driver_lock_held(9), drm_gpusvm_find_vma_start(9), drm_gpusvm_range_find_or_insert(9), __drm_gpusvm_unmap_pages(9), __drm_gpusvm_free_pages(9), drm_gpusvm_free_pages(9), drm_gpusvm_range_remove(9), drm_gpusvm_range_get(9), drm_gpusvm_range_destroy(9), drm_gpusvm_range_put(9), drm_gpusvm_pages_valid(9), drm_gpusvm_pages_valid_unlocked(9), drm_gpusvm_get_pages(9), drm_gpusvm_unmap_pages(9), drm_gpusvm_has_mapping(9), drm_gpusvm_range_set_unmapped(9)

like I said. whole friend group. go say hi 👋💜

---

ngl bestie, if you're poking around GPU SVM ranges, read the Overview(9) and Locking(9) entries first. no notes. 💅

---

and that's the page!! sourced from ./drivers/gpu/drm, dated October 2026 — mwah, go evict some ranges responsibly 🌈✨👑