radeon_sync_rings(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay bestie, welcome to the Kernel API Manual β€” you're looking at radeon_sync_rings(9), and the name is literally radeon_sync_rings β€” sync ring to all registered fences. that's the whole assignment, and it ate. πŸ’…βœ¨


πŸŽ€ SYNOPSIS πŸŽ€

here's the signature, copied exactly because we do not play with code, fr fr:

int radeon_sync_rings (struct radeon_device *rdev , struct radeon_sync
*sync , int ring );

πŸ’– ARGUMENTS πŸ’–

  • rdev β€” radeon_device pointer. that's the device pointer, bestie.
  • sync β€” sync object to use. yes, use it.
  • ring β€” ring that needs sync. this ring is the one asking for the sync glow-up. πŸ’«

πŸ¦‹ DESCRIPTION πŸ¦‹

so the mission, should you choose to accept it: ensure that all registered fences are signaled before letting the ring continue. that's it. that's the plot. make sure every registered fence is signaled first, then the ring can keep on rolling. πŸ”₯

🚨 important caveat, no cap: the caller must hold the ring lock. the caller. must. hold. the ring lock. do not skip this, bestie. πŸ”’

🌈 SEE ALSO 🌈


mwah πŸ’‹ sign-off time: this page is from ./drivers/gpu/drm/radeon, dated October 2026, and it's the radeon_sync_rings(9) page. bye bestie, go hold that ring lock. πŸŽ€βœ¨

πŸ“¦ where this page comes from