xe_vm_find_vma_by_addr(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_vm_find_vma_by_addr — find a VMA by its address 🎀

okay so this one's a page from the Kernel API Manual bestie, and it's honestly so straightforward it's kind of iconic for it. You got a vm, you got an address, and you're like "hey which VMA lives here?" and it tells you. That's the whole plot. No cap. ✨

🌸 SYNOPSIS 🌸

struct xe_vma * xe_vm_find_vma_by_addr (struct xe_vm *vm , u64 page_addr
);

literally just hand it those two things and it hands you back a struct xe_vma *. the way that signature just sits there, all neat and symmetric 🫶

✨ ARGUMENTS ✨

  • vm — the xe_vm that the vma belongs to 💜 like, which VM's little neighborhood are we even searching in
  • page_addr — the address you're looking up 🔍 the actual thing you're tryna find

that's it. that's the whole input list. two arguments, zero drama, main character energy fr fr 👑

🦋 SEE ALSO 🦋

okay this is the part where the page goes FULL group chat and tags everyone in the VM source file. the kernel file is ./drivers/gpu/drm/xe/xe_vm.c and it is throwing a party, here's the guest list:

yes bestie I listed every single one, we don't do "etc." around here 💅 (also yes, struct xe_vma_lock_and_validate_flags(9) really is written like that in the source page — I'm not touching it, that's a them thing 🙈)

🫶 tiny reminder: this page is just the finder. it looks stuff up. it does not lock, bind, kill, or otherwise start anything — for that you gotta go knock on the doors up in SEE ALSO.

and that's the tea 🍓 source lives in ./drivers/gpu/drm/xe, this lil page is dated October 2026, and it goes by xe_vm_find_vma_by_addr(9) — mwah, slay, see you in the next man page 💖✨🎀

📦 where this page comes from