radeon_vm_grab_id(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… radeon_vm_grab_id(9) β€” from the Kernel API Manual, bestie ✨

okay so picture this: it's a kernel API manual page, section 9, and the star of the show is radeon_vm_grab_id. she's a function. she grabs IDs. she's iconic. let's get into it πŸŽ€


✨ NAME ✨

radeon_vm_grab_id β€” grab the next free VMID, no cap 🫢


🌸 SYNOPSIS 🌸

struct radeon_fence * radeon_vm_grab_id (struct radeon_device *rdev ,
struct radeon_vm *vm , int ring );

that's the whole signature, copy it exactly please, she's precise πŸ’–


πŸ¦‹ ARGUMENTS πŸ¦‹

  • rdev β€” a radeon_device pointer, aka the whole GPU situation πŸ‘‘
  • vm β€” the vm we're allocating an id for, main character energy fr
  • ring β€” the ring we want to submit the job to, that's the vibe check πŸ’«

πŸ”₯ DESCRIPTION πŸ”₯

so like, this function allocates an id for the vm β€” and this is cayman+ only, iykyk πŸ’…. it returns the fence we need to sync to (if any). yes, if any, that's important, sometimes there just isn't one, and that's fine 🌈

⚠️ bestie listen to me. Global and local mutex must be locked! both of them. not one. not "eh probably". both. this is not a drill 😭

πŸ’œ SEE ALSO πŸ’œ

the kernel file lives at ./drivers/gpu/drm/radeon/radeon_vm.c and honestly she has a whole friend group, here's the full squad, go say hi 🫢:


okay that's the whole page, ily, go lock those mutexes and slay πŸ’…βœ¨

this lil cutie comes to you from ./drivers/gpu/drm/radeon, dated October 2026 β€” periodt, that's the source and the date, mwah πŸ“πŸ’‹

πŸ“¦ where this page comes from