amdgpu_sync_move(9)
π amdgpu_sync_move β ngl bestie, this one's a whole relocation era
okay so like, welcome to the Kernel API Manual β¨ this page is amdgpu_sync_move(9) and honestly? it's giving "I'm just gonna move these fences real quick" and we're obsessed π
πΈ NAME πΈ
amdgpu_sync_move β move all the fences from src to dst π¦
like, every single one. no fence left behind. periodt π
β¨ SYNOPSIS β¨
void amdgpu_sync_move (struct amdgpu_sync *src , struct amdgpu_sync *dst );
look at that signature. flawless. no return value because she doesn't need to report back, she just does it π
π«Ά ARGUMENTS π«Ά
srcβ the source of the fences. heads up bestie: this bad girl is empty after the function returns π she gave everything she had.dstβ the destination for the fences. this is where all the fences end up living their best life π
π₯ DESCRIPTION π₯
so the vibe is: amdgpu_sync_move moves all the fences from source to destination. like, all of them. the whole collection. the entire fence ecosystem π
but here's the tea β β every fence that was already chilling in destination gets freed π©Έ like, gone. released. not invited to the afterparty. and source is left empty after the function call, because she transferred everything she owned.
so to recap, in order:
- fences from
srcβ moved todstπ - fences already in
dstβ freed π srcafterwards β empty, thriving, unbothered π§
fr fr, this is highkey a "clean slate" moment for src and a "new management" moment for dst. iconic behavior, no notes π
π SEE ALSO π
the kernel file that runs this whole situation lives at ./drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c β go read it, iykyk π
and the whole sync-fence friend group, all of them linked so you can go down the rabbit hole π:
amdgpu_sync_create(9), amdgpu_sync_same_dev(9), amdgpu_sync_get_owner(9), amdgpu_sync_keep_later(9), amdgpu_sync_add_later(9), amdgpu_sync_fence(9), amdgpu_sync_resv(9), amdgpu_sync_kfd(9), amdgpu_sync_peek_fence(9), amdgpu_sync_get_fence(9), amdgpu_sync_clone(9), amdgpu_sync_push_to_job(9), amdgpu_sync_free(9), amdgpu_sync_init(9), amdgpu_sync_fini(9)
β οΈ friendly reminder bestie: those fences sitting in dst before you call this? yeah, they get freed. that's real. don't be surprised when they're gone π
and that's the whole page, mwah π sign-off time: this one came from ./drivers/gpu/drm/amd/amdgpu, dated October 2026, and it's filed under amdgpu_sync_move(9) π stay slay, stay synced, and remember β fences are temporary but good documentation is forever β¨π
π¦ 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