xe_svm_find_vma_start(9)

🌸 NAME 🌸

xe_svm_find_vma_start — Find start of CPU VMA. This is the Kernel API Manual page for xe_svm_find_vma_start(9), bestie 💖

---

✨ SYNOPSIS ✨

u64 xe_svm_find_vma_start (struct xe_vm *vm , u64 start , u64 end ,
struct xe_vma *vma );

---

🎀 ARGUMENTS 🎀

• vm — the xe_vm pointer, aka the VM we're digging around in 🫶
• start — the start address of the range, periodt ✨
• end — the end address of the range, no cap 🌸
• vma — a pointer to struct xe_vma, the VMA in question 💅

---

🦋 DESCRIPTION 🦋

OK so this function searches for a cpu vma, within the specified range [start, end] in the given VM. It adjusts the range based on the xe_vma start and end addresses. If no cpu VMA is found, it returns ULONG_MAX. That's the whole vibe — very targeted, very demure 😌✨

---

🔥 RETURN 🔥

It gives you the starting address of the VMA within the range, or ULONG_MAX if no VMA is found. So either you get your address or you get the big ULONG_MAX energy 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/xe/xe_svm.c
• drm_pagemap reference-counting in xe:(9)
• xe_svm_init(9)
• xe_svm_close(9)
• xe_svm_fini(9)
• xe_svm_range_validate(9)
• xe_svm_range_needs_migrate_to_vram(9)
• xe_svm_handle_pagefault(9)
• xe_svm_has_mapping(9)
• xe_svm_unmap_address_range(9)
• xe_svm_bo_evict(9)
• xe_svm_range_find_or_insert(9)
• xe_svm_range_get_pages(9)
• xe_svm_ranges_zap_ptes_in_range(9)
• xe_vma_resolve_pagemap(9)
• xe_svm_alloc_vram(9)
• xe_pagemap_create(9)
• xe_pagemap_find_or_create(9)
• xe_pagemap_shrinker_create(9)
• xe_pagemap_cache_create(9)
• xe_drm_pagemap_from_fd(9)
• xe_svm_flush(9)

---

Catch you in ./drivers/gpu/drm/xe — October 2026 — xe_svm_find_vma_start(9) 💅🎀✨