STRUCT DRM_GPUVA_OP_UNMAP(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

Okay bestie, welcome to the struct drm_gpuva_op_unmap(9) page from the Kernel API Manual β€” this is the lil struct that represents one single unmap operation, and we’re gonna get you comfy with it. πŸ’–

πŸ’… NAME πŸ’…

struct drm_gpuva_op_unmap β€” GPU VA unmap operation. That’s the whole vibe: one unmap operation, no cap. ✨

πŸ¦‹ SYNOPSIS πŸ¦‹

       struct drm_gpuva_op_unmap {
           struct drm_gpuva *va;
           bool keep;
        };

πŸŽ€ Members πŸŽ€

  • va β€” the drm_gpuva to unmap. Literally the thing getting unmapped, bestie. πŸ‘‘
  • keep β€” Indicates whether this drm_gpuva is physically contiguous with the original mapping request. Yes, that’s the whole flag vibe. πŸ’…

Optionally, if keep is set, drivers may keep the actual page table mappings for this drm_gpuva, adding the missing page table entries only and update the drm_gpuvm accordingly. So it’s giving β€œreuse what’s already there” energy β€” but only optionally, and only when keep is set. 🫢

🌸 Description 🌸

This structure represents a single unmap operation generated by the DRM GPU VA manager. One struct, one unmap op, main character energy. 😭✨

🌈 SEE ALSO 🌈

Kernel file ./include/drm/drm_gpuvm.h β€” and honestly the whole friend group is here:


Byeeee from <purple>./include/drm</purple>, dated October 2026, on the struct drm_gpuva_op_unmap(9) page β€” mwah πŸ’‹πŸ’œ

πŸ“¦ where this page comes from