xe_vm_validation_exec(9)

💅 xe_vm_validation_exec(9) 💅

okay so bestie, welcome to the Kernel API Manual — today we're reading xe_vm_validation_exec, and it's giving “I'm just an accessor but I know things” energy ✨.

🌸 NAME 🌸

xe_vm_validation_exec — Accessor to read the drm_exec object. No cap, that's the whole vibe. 💖

✨ SYNOPSIS ✨

struct drm_exec * xe_vm_validation_exec (struct xe_vm *vm );

🎀 ARGUMENTS 🎀

• vm — The vm we want to register a drm_exec object with. That's it, that's the argument 🫶

💖 RETURN 💖

The drm_exec object used to lock the vm's resv. The value is a valid pointer, NULL, or one of the special values defined in xe_validation.h.

bestie, clock the range: valid pointer, NULL, or a special value from xe_validation.h — don't go assuming it's always a plain pointer, okay? 😭

👑 SEE ALSO 👑

Kernel file ./drivers/gpu/drm/xe/xe_vm.h and the whole squad:

• MAX_FAULTS_SAVED_PER_VM(9)
• xe_vm_has_scratch(9)
• gpuvm_to_vm(9)
• Provide accessors for vma members to facilitate easy change of(9)
• to_userptr_vma(9)
• xe_vm_reactivate_rebind(9)
• xe_vm_resv(9)
• xe_vm_assert_held(9)
• xe_vm_set_validating(9)
• xe_vm_clear_validating(9)
• xe_vm_is_validating(9)
• xe_vm_set_validation_exec(9)
• xe_vm_has_valid_gpu_mapping(9)

mwah 💋 this cutie's source/version lives at ./drivers/gpu/drm/xe, the date is October 2026, and the footer title is xe_vm_validation_exec(9). that's the page, bestie — periodt. 🫶✨