xe_vm_set_validation_exec(9)

💖 xe_vm_set_validation_exec(9) 💖

Okay bestie, we're in the Kernel API Manual for this one — yes, the actual Kernel API Manual, keep up 💅.

🌸 NAME 🌸

xe_vm_set_validation_exec — accessor to set the drm_exec object. Iconic little setter, no cap.

✨ SYNOPSIS ✨

void xe_vm_set_validation_exec (struct xe_vm *vm , struct drm_exec *exec
);

🎀 ARGUMENTS 🎀

• vm — the vm we want to register a drm_exec object with. Your main character vm, basically.
• exec — the exec object we want to register. The exec in question, periodt.

💅 DESCRIPTION 💅

Set the drm_exec object used to lock the vm's resv. That's the whole vibe check: this is the accessor that puts that exec object in place, fr fr.

🔥 SEE ALSO 🔥

Kernel file ./drivers/gpu/drm/xe/xe_vm.h, plus the whole friend group:

• 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_validation_exec(9)
• xe_vm_has_valid_gpu_mapping(9)

And that's the page, bestie 🫶. Cute sign-off: this one lives under ./drivers/gpu/drm/xe, dated October 2026, and it's literally called xe_vm_set_validation_exec(9) — slay 💖✨