xe_vm_find_c...or_vma_range(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_vm_find_cpu_addr_mirror_vma_range(9)

okay so bestie, welcome to the kernel API manual for xe_vm_find_cpu_addr_mirror_vma_range — yes that name is a whole mouthful, no I will not be shortening it, and yes it is iconic. this is a real function in the kernel's 9 section and we're gonna get you fluent in it. 🎀

✨ NAME ✨

xe_vm_find_cpu_addr_mirror_vma_range — the glow-up function that extends a VMA range to include adjacent CPU-mirrored VMAs. literally its whole job. periodt. 💅

🌸 SYNOPSIS 🌸

void xe_vm_find_cpu_addr_mirror_vma_range (struct xe_vm *vm , u64 *start
, u64 *end );

like, that's the signature, copy it exactly, don't be weird about it. ✨

🦋 ARGUMENTS 🦋

  • vm — the VM you're searching inside. this is your main character struct, the whole search happens in here. 👑
  • start — an input/output pointer to the starting address of the range. yeah, in and out — it goes in with a value and can come back changed. 🔁
  • end — an input/output pointer to the end address of the range. same deal, it's a two-way street bestie. 🔁

💖 DESCRIPTION 💖

okay so here's the vibe, and it's actually kind of elegant ngl:

given a range defined by start and range, this function checks the VMAs immediately before and immediately after the range. just the two neighbors, mind you — it's not out here scanning the whole world. 🧚

if those neighboring VMAs are CPU-address-mirrored and have default memory attributes, then — and this is the slay part — the function updates start and range to include them. so the range grows to swallow its cute little neighbors. 🌈

this extended range can then be used for merging or other operations that require a unified VMA. it's giving "prep work" energy and honestly? we respect it. 🫶

⚠️ important caveat bestie: the function does not perform the merge itself — it only computes the mergeable boundaries. it's setting the table, not eating the meal. do not come for this function expecting the merge to already be done. 💀

🔥 SEE ALSO 🔥

the source of all this magic lives in the kernel file ./drivers/gpu/drm/xe/xe_vm.c, and here's the full squad of related functions — every single one, no gatekeeping:

like, that's the whole friend group. go say hi. iykyk. 🫶✨

🎀 SIGN-OFF 🎀

and that's the tea! this page ships out of ./drivers/gpu/drm/xe, dated October 2026, and is filed under xe_vm_find_c...or_vma_range(9) — yes the header truncates it, no that's not a typo on my end, that's just how it's printed. 💜

go extend those ranges bestie, you've got this. 🦋🌸💅

📦 where this page comes from