xe_vm_alloc...r_mirror_vma(9)

okay bestie, welcome to the Kernel API Manual page for xe_vm_alloc_cpu_addr_mirror_vma(9). Hydrate, stretch, and let's get into it 🫶✨

💖 NAME 💖

xe_vm_alloc_cpu_addr_mirror_vma — Allocate CPU addr mirror vma. That's the whole name, no cap; it literally allocates a CPU addr mirror vma 💅

✨ SYNOPSIS ✨

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

🎀 ARGUMENTS 🎀

• vm — pointer to the xe_vm structure, bestie 🫶
• start — starting input address, literally where the input starts ✨
• range — size of the input range, aka how much range we're ranging 🌸

🦋 DESCRIPTION 🦋

okay so what this function does: it splits/merges existing vma to create a new vma for the user provided input range. That's the vibe, that's the job, periodt 🦋✨

⭐ RETURN ⭐

0 if success. That's the return tea: success gives you 0 🔥

🌈 SEE ALSO 🌈

Kernel file: ./drivers/gpu/drm/xe/xe_vm.c — that's the source file, iykyk 💅

the whole see-also squad, no skips:

• 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) — yes bestie, the original list has that struct token right before this one, so here it is in all its chaotic glory 🙈
• 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_alloc_madvise_vma(9)
• xe_vm_find_cpu_addr_mirror_vma_range(9)
• xe_vm_add_exec_queue(9)
• xe_vm_remove_exec_queue(9)

Source/version: ./drivers/gpu/drm/xe · date: October 2026 · page: xe_vm_alloc...r_mirror_vma(9). k bye bestie, go alloc that mirror vma responsibly 💖✨