xe_svm_range_find_or_insert(9)

📦 version 7.3.1, in nixpkgs unstable

💅 xe_svm_range_find_or_insert — bestie edition 🦋

okay so welcome to the xe_svm_range_find_or_insert(9) page, part of the Kernel API Manual (yes that Kernel API Manual, the one we all fear and love 💀). This is that GPU SVM range business. Sit down, hydrate, let's go.

✨ NAME ✨

xe_svm_range_find_or_insert — literally the function that finds or inserts a GPU SVM range 🎀

🌸 SYNOPSIS 🌸

keep it exactly like this, no cap:

struct xe_svm_range * xe_svm_range_find_or_insert (struct xe_vm *vm ,
u64 addr , struct xe_vma *vma , struct drm_gpusvm_ctx *ctx );

🫶 ARGUMENTS 🫶

  • vm — an xe_vm pointer. the whole vm situation, iconic.
  • addr — the address for which the range needs to be found/inserted. this is the address. it's giving "where is it" energy.
  • vma — pointer to struct xe_vma which mirrors CPU. like, it's the vma's reflection selfie 🙈
  • ctx — the GPU SVM context. the vibe holder.

💖 DESCRIPTION 💖

so what does it even do?? it finds — OR inserts — a newly allocated SVM range, based on the address. that's it. that's the whole thing. find or insert, based on addr. slay. ⭐

🔥 RETURN 🔥

  • Pointer to the SVM range on success 🎉
  • ERR_PTR on failure 😭

(so like, check your pointer bestie, don't just vibe with it blindly.)

👑 SEE ALSO 👑

look at this friend group. it's a whole squad:

ok real talk: they all live in ./drivers/gpu/drm/xe together, it's basically a group chat 🧚

and that's the page!! mwah 💋 this lil manual came from ./drivers/gpu/drm/xe and it's dated October 2026, so like, from the future?? we love a forward-thinking source. anyway xe_svm_range_find_or_insert(9) out. bye bestie, go find (or insert) your range 💜✨

📦 where this page comes from