radeon_ring_test_lockup(9)
π radeon_ring_test_lockup β like, the Kernel API Manual edition, bestie
Okay so picture this: it's a page from the Kernel API Manual all about radeon_ring_test_lockup, and it's literally just one job β checking whether a ring is locked up by, yep, recording information. That's the whole vibe. β¨
π NAME π
radeon_ring_test_lockup β check if ring is lockedup by recording information
No cap, that's the entire mission statement. She records stuff so you can tell if the ring has given up on life. π
πΈ SYNOPSIS πΈ
bool radeon_ring_test_lockup (struct radeon_device *rdev , struct radeon_ring *ring );
Returns a bool, takes two pointers, that's it, that's the whole function. Slay. π«Ά
π¦ ARGUMENTS π¦
rdevβ the radeon device structure. Like, the big picture device object, the main character of the whole driver. πringβ theradeon_ringstructure holding ring information. This is the one we're side-eyeing to see if it's locked up. π
π SEE ALSO π
Kernel file ./drivers/gpu/drm/radeon/radeon_ring.c β go read the source, iykyk π
And the whole ring squad, fr fr:
radeon_ring_supports_scratch_reg(9)radeon_ring_free_size(9)radeon_ring_alloc(9)radeon_ring_lock(9)radeon_ring_commit(9)radeon_ring_unlock_commit(9)radeon_ring_undo(9)radeon_ring_unlock_undo(9)radeon_ring_lockup_update(9)radeon_ring_backup(9)radeon_ring_restore(9)radeon_ring_init(9)radeon_ring_fini(9)
π Okay bestie, that's the whole page! Shoutout to ./drivers/gpu/drm/radeon for being the source, October 2026 for the date, and the Kernel API Manual for hosting this iconic little function. Go check your rings, 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