xe_vm_alloc_madvise_vma(9)

💖 NAME 💖

Bestie, welcome to the xe_vm_alloc_madvise_vma(9) page from the Kernel API Manual ✨ This one is xe_vm_alloc_madvise_vma — and its whole deal is Allocate VMA's with madvise ops 💅

---

🌸 SYNOPSIS 🌸

int xe_vm_alloc_madvise_vma (struct xe_vm *vm , uint64_t start ,
uint64_t range );

---

🎀 ARGUMENTS 🎀

• vm — Pointer to the xe_vm structure 🫶
• start — Starting input address ⭐
• range — Size of the input range 🦋

---

✨ DESCRIPTION ✨

Okay so this function splits an existing vma to create a new vma for the user-provided input range 💖 That’s the vibe — split, make new vma, slay. No cap, that’s the whole description 😭

---

🔥 RETURN 🔥

Returns 0 if success 👑 Periodt.

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpu/drm/xe/xe_vm.c 🧚
• xe_vm_drm_exec_lock(9)
• xe_vm_remove_compute_exec_queue(9)
• xe_vm_kill(9)
• xe_vm_validate_rebind(9)
• xe_vm_bump_lru(9)
• xe_vm_resume_rebind_worker(9)
• xe_vm_add_fault_entry_pf(9)
• xe_vm_range_rebind(9)
• xe_vm_range_unbind(9)
• xe_vma_mem_attr_copy(9)
• xe_vm_lock_vma(9)
• xe_vm_create_scratch(9)
• xe_vm_find_vma_by_addr(9)
• xe_vma_has_default_mem_attrs(9)
• struct xe_vma_lock_and_validate_flags(9)
• xe_vm_bind_kernel_bo(9)
• xe_vm_lock(9)
• xe_vm_unlock(9)
• xe_vm_invalidate_vma_submit(9)
• xe_vm_invalidate_vma(9)
• xe_vma_need_vram_for_atomic(9)
• xe_vm_find_cpu_addr_mirror_vma_range(9)
• xe_vm_alloc_cpu_addr_mirror_vma(9)
• xe_vm_add_exec_queue(9)
• xe_vm_remove_exec_queue(9)

---

Okay bestie, that’s the page 💖 Source/version: ./drivers/gpu/drm/xe — date: October 2026 — page: xe_vm_alloc_madvise_vma(9). Bye 🫶✨