amdgpu_cs_wait_any_fence(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ amdgpu_cs_wait_any_fence(9) ✨

okay so bestie, welcome to the Kernel API Manual β€” this is the page for the kernel function amdgpu_cs_wait_any_fence, and honestly we're just gonna vibe through it together πŸ’…


πŸŽ€ NAME πŸŽ€

amdgpu_cs_wait_any_fence β€” wait on any fence to signal πŸ‘‘

like… any of them. one single fact of a fence doing its thing and you are OUT of there. periodt. πŸƒβ€β™€οΈπŸ’¨


πŸ¦‹ SYNOPSIS πŸ¦‹

int amdgpu_cs_wait_any_fence (struct amdgpu_device *adev , struct
drm_file *filp , union drm_amdgpu_wait_fences *wait , struct
drm_amdgpu_fence *fences );

it's giving "four arguments, one int, no notes" 😌 the return type is int, that's the whole personality of this function signature ngl ✨


🌸 ARGUMENTS 🌸

  • adev β€” the amdgpu device πŸ’– like, the actual piece of hardware energy, main character of the whole scene fr fr
  • filp β€” file private 🫢 the DRM file-private situation, yk how it is
  • wait β€” wait parameters ⏳ everything you need to know about the waiting is in here, it's a union drm_amdgpu_wait_fences *
  • fences β€” array of drm_amdgpu_fence πŸ”₯ an actual array, bestie, plural fences, because we're waiting on ANY of them, iykyk

🧚 SEE ALSO 🧚

heads up bestie: amdgpu_cs_wait_all_fences(9) is the sibling that waits on all of them β€” any vs all, know the difference or perish πŸ’€ this page is the any one, keep it straight πŸ™ˆ

🌈 and that's the whole page, no crumbs left, we ate πŸ“

drop a 🫢 for the Kernel API Manual, brought to you by the lovely people down at ./drivers/gpu/drm/amd/amdgpu β€” see you in October 2026, mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from