drm_gpuvm_e...sv_add_fence(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

Okay so this page is for drm_gpuvm_exec_resv_add_fence(9), and it comes from the Kernel API Manual β€” the header’s title is drm_gpuvm_e...sv_add_fence(9), if you were wondering why it looks like that.

The main-character function is drm_gpuvm_exec_resv_add_fence β€” add fence to private and all extobj. That’s the whole vibe. πŸ’…


✨ SYNOPSIS ✨

void drm_gpuvm_exec_resv_add_fence (struct drm_gpuvm_exec *vm_exec ,
struct dma_fence *fence , enum dma_resv_usage private_usage , enum
dma_resv_usage extobj_usage );

🌸 ARGUMENTS 🌸

  • vm_exec β€” the drm_gpuvm_exec wrapper, bestie.
  • fence β€” the fence to add. Slay.
  • private_usage β€” private dma-resv usage.
  • extobj_usage β€” extobj dma-resv usage.

πŸ¦‹ DESCRIPTION πŸ¦‹

See drm_gpuvm_resv_add_fence.

That’s literally it, no cap β€” the manual is pointing you over there for the full explanation. Go get the tea from that page. 🫢


πŸ‘‘ SEE ALSO πŸ‘‘

The whole friend group plus the kernel file is right here:


That’s the page, bestie 🫢 Cute little sign-off: source/version is ./include/drm, dated October 2026, and the header/footer title is drm_gpuvm_e...sv_add_fence(9). Mwah πŸ’œπŸŽ€

πŸ“¦ where this page comes from