amdgpu_cs_wait_any_fence(9)
β¨ 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 frfilpβ file private π«Ά the DRM file-private situation, yk how it iswaitβ wait parameters β³ everything you need to know about the waiting is in here, it's aunion drm_amdgpu_wait_fences *fencesβ array ofdrm_amdgpu_fenceπ₯ an actual array, bestie, plural fences, because we're waiting on ANY of them, iykyk
π§ SEE ALSO π§
- Kernel file
./drivers/gpu/drm/amd/amdgpu/amdgpu_cs.cβ the source, the origin story, the mothership πΈ amdgpu_cs_wait_ioctl(9)amdgpu_cs_get_fence(9)amdgpu_cs_wait_all_fences(9)amdgpu_cs_wait_fences_ioctl(9)amdgpu_cs_find_mapping(9)
heads up bestie:amdgpu_cs_wait_all_fences(9)is the sibling that waits on all of them βanyvsall, know the difference or perish π this page is theanyone, 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms