xe_vm_has_scratch(9)

💅 xe_vm_has_scratch(9)

okay so this is a page straight out of the Kernel API Manual, and honestly? it's a tiny little icon and i'm obsessed with how simple it is.

---

✨ NAME ✨

xe_vm_has_scratch — literally just tells you whether the vm is configured for scratch PTEs. that's it. that's the whole vibe check. 🫶

---

🌸 SYNOPSIS 🌸

bool xe_vm_has_scratch (const struct xe_vm *vm );

one function, one argument, returns a bool. short and sweet, no cap. 💖

---

🎀 ARGUMENTS 🎀

• vm — The vm. that's the whole description bestie, the manpage is being very main-character-minimal about it. it's a const struct xe_vm *, so like, nobody's mutating it on your watch. 🔥

---

🦋 RETURN 🦋

returns whether the vm populates unmapped areas with scratch PTEs. like, is it filling in the blank spots with scratch pages or nah? that's the whole answer. ✨

ngl this page is short enough that there's zero excuse to not read all of it. iykyk.

---

💜 SEE ALSO 💜

okay this is where it goes OFF, look at this list, we're linking the whole friend group:

• Kernel file ./drivers/gpu/drm/xe/xe_vm.h MAX_FAULTS_SAVED_PER_VM(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_validation_exec(9)
• xe_vm_has_valid_gpu_mapping(9)

and yeah, that third one really does look like that in the original — i'm not touching it, that's between the manpage and god. 💀

---

okay that's the whole page, ily, go read xe_vm.h 💅✨

this cutie came out of ./drivers/gpu/drm/xe, dated October 2026 — see you there, bestie! 🌈⭐🍓