drm_gpuvm_p...h_ops_create(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 drm_gpuvm_prefetch_ops_create 💅

okay bestie, this one comes straight out of your Kernel API Manual, so you already know it's giving "I write C for a living and I still have a personality." Let's get into it ✨

💖 NAME 💖

drm_gpuvm_prefetch_ops_create — literally creates the &drm_gpuva_ops you need to prefetch. that's the whole vibe. no notes. 🫶

⭐ SYNOPSIS ⭐

struct drm_gpuva_ops * drm_gpuvm_prefetch_ops_create (struct drm_gpuvm
*gpuvm , u64 addr , u64 range );

yes she's a pointer-returning queen, we love to see it 👑

🎀 ARGUMENTS 🎀

  • gpuvm — the drm_gpuvm that reps the GPU VA space. your whole address-space situation lives here 💜
  • addr — the start address of the range you wanna prefetch. where the party begins 📍
  • range — the range of the mappings to prefetch. how far the party goes 🔥

🦋 DESCRIPTION 🦋

so what does this bad girl do?? she creates a list of operations to perform prefetching. that's it, that's her job, and she ate 💅

you can iterate that list with drm_gpuva_for_each_op, and bestie, listen — it must be processed in the given order. no skipping ahead, no main character free-styling, the order is the order fr fr ⚠️

the list can contain prefetch operations, and ngl there can be an arbitrary amount of them. as many as it takes. no cap. 🌈

🚨 important bestie PSA: after you're done processing the returned drm_gpuva_ops, you must free it with drm_gpuva_ops_free. do not leave it lying around like a forgotten iced coffee. that's a memory leak and we don't do those here 🙈

✨ RETURN ✨

a pointer to the drm_gpuva_ops on success 💖 — or an ERR_PTR on failure 😭. check it. always check it. iykyk 🧚

👑 SEE ALSO 👑

the whole extended friend group, literally:

and that's the whole page bestie!! 🍓

this icon lives in ./drivers/gpu/drm and the version on deck is October 2026 — so like, future-dated slay 💀✨ mwah, go free your ops 🫶💖

📦 where this page comes from