STRUCT DRM_GPUVA(9)

✨ struct drm_gpuva(9) ✨

okay so bestie, welcome to the Kernel API Manual — this is the page for struct drm_gpuva, and it's literally the blueprint for tracking a GPU VA mapping. buckle up 💅

---

🌸 NAME 🌸

struct drm_gpuva — the structure that tracks a GPU VA mapping 🎀

---

✨ SYNOPSIS ✨

struct drm_gpuva {
    struct drm_gpuvm *vm;
    struct drm_gpuvm_bo *vm_bo;
    enum drm_gpuva_flags flags;
    struct {
      u64 addr;
      u64 range;
    } va;
    struct {
      u64 offset;
      struct drm_gem_object *obj;
      struct list_head entry;
    } gem;
    struct {
      struct rb_node node;
      struct list_head entry;
      u64 __subtree_last;
    } rb;
 };

---

🫶 Members 🫶

the top-level fields

• vm — the drm_gpuvm this object is associated with. it's giving "who's your parent" energy 👑
• vm_bo — the drm_gpuvm_bo abstraction for the mapped drm_gem_object
• flags — the drm_gpuva_flags for this mapping 🚩
• va — structure containing the address and range of the drm_gpuva
  • va.addr — the start address 📍

the gem struct

• gem — structure containing the drm_gem_object and its offset
  • gem.offset — the offset within the drm_gem_object
  • gem.obj — the mapped drm_gem_object 🧚
  • gem.entry — the list_head to attach this object to a drm_gpuvm_bo

the rb struct

• rb — structure containing data to store drm_gpuvas in a rb-tree 🌈
  • rb.node — the rb-tree node
  • rb.entry — The list_head to additionally connect drm_gpuvas in the same order they appear in the interval tree. This is useful to keep iterating drm_gpuvas from a start node found through the rb-tree while doing modifications on the rb-tree itself. no cap, this one's the MVP for mutation-safe loops 🔥
  • rb.__subtree_last — needed by the interval tree, holding last-in-subtree

---

💖 Description 💖

This structure represents a GPU VA mapping and is associated with a drm_gpuvm.

Typically, this structure is embedded in bigger driver structures. like, it's not out here living its own main character life — it's a supporting icon inside your driver's structs 🎀

---

🌟 SEE ALSO 🌟

Kernel file ./include/drm/drm_gpuvm.h — and honestly the whole friend group:

• enum drm_gpuva_flags(9)
• drm_gpuva_invalidate(9)
• drm_gpuva_invalidated(9)
• enum drm_gpuvm_flags(9)
• struct drm_gpuvm(9)
• drm_gpuvm_get(9)
• drm_gpuvm_resv_protected(9)
• drm_gpuvm_immediate_mode(9)
• drm_gpuvm_resv(9)
• drm_gpuvm_resv_obj(9)
• drm_gpuvm_is_extobj(9)
• drm_gpuvm_for_each_va_range(9)
• drm_gpuvm_for_each_va_range_safe(9)
• drm_gpuvm_for_each_va(9)
• drm_gpuvm_for_each_va_safe(9)
• struct drm_gpuvm_exec(9)
• drm_gpuvm_exec_unlock(9)
• drm_gpuvm_exec_resv_add_fence(9)
• drm_gpuvm_exec_validate(9)
• struct drm_gpuvm_bo(9)
• drm_gpuvm_bo_get(9)
• drm_gpuvm_bo_gem_evict(9)
• drm_gpuvm_bo_for_each_va(9)
• drm_gpuvm_bo_for_each_va_safe(9)
• enum drm_gpuva_op_type(9)
• struct drm_gpuva_op_map(9)
• struct drm_gpuva_op_unmap(9)
• struct drm_gpuva_op_remap(9)
• struct drm_gpuva_op_prefetch(9)
• struct drm_gpuva_op(9)
• struct drm_gpuva_ops(9)
• drm_gpuva_for_each_op(9)
• drm_gpuva_for_each_op_safe(9)
• drm_gpuva_for_each_op_from_reverse(9)
• drm_gpuva_for_each_op_reverse(9)
• drm_gpuva_first_op(9)
• drm_gpuva_last_op(9)
• drm_gpuva_prev_op(9)
• drm_gpuva_next_op(9)
• struct drm_gpuvm_map_req(9)
• struct drm_gpuvm_ops(9)
• drm_gpuva_op_remap_to_unmap_range(9)

---

this page lives in ./include/drm, and it's dated October 2026 — the manual name on the tin is struct drm_gpuva(9), and that's the whole vibe check. periodt 💅💖