STRUCT XE_VMA_LOCK_AND_VALIDATE_FLAGS(9)

okay bestie, welcome to the struct xe_v...lidate_flags(9) page from the Kernel API Manual 💅✨

🌸 NAME 🌸

struct xe_vma_lock_and_validate_flags — Flags for vma_lock_and_validate() 🎀

✨ SYNOPSIS ✨

Here's the struct in all its 1-bit-flag glory, verbatim:

       struct xe_vma_lock_and_validate_flags {
           u32 res_evict : 1;
           u32 validate : 1;
           u32 request_decompress : 1;
           u32 check_purged : 1;
        };

👑 Members 👑

This is a bundle of four u32 ... : 1 flags, and every single one has a job. The vibes are extremely specific:

• res_evict — Allow evicting resources during validation. That's the whole assignment, bestie.
• validate — Perform BO validation. Yep, it does exactly what it says on the label.
• request_decompress — Request BO decompression. respectfully requesting the decompression, no cap.
• check_purged — Reject operation if BO is DONTNEED or PURGED. it's giving gatekeeping, but make it correctness 🫶

🔥 SEE ALSO 🔥

Kernel file ./drivers/gpu/drm/xe/xe_vm.c is the main-character file, and the related function lore is:

• 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)
• 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_alloc_cpu_addr_mirror_vma(9)
• xe_vm_add_exec_queue(9)
• xe_vm_remove_exec_queue(9)

okay that's the whole page, bestie 🫶💖 — source/version: ./drivers/gpu/drm/xe, date: October 2026, and the page is struct xe_v...lidate_flags(9). slay and stay validated ✨