radeon_vm_bo_set_addr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ radeon_vm_bo_set_addr(9) πŸ’œ

okay so this is a page straight out of the Kernel API Manual, bestie β€” it's radeon_vm_bo_set_addr(9) and it's literally the glow-up where a buffer object gets told where to sit inside a virtual memory space. sit down, this is gonna be good πŸŽ€


✨ NAME ✨

radeon_vm_bo_set_addr β€” set bos virtual address inside a vm

like. the whole entire job. that's it. that's the function 🫢


✨ SYNOPSIS ✨

int radeon_vm_bo_set_addr (struct radeon_device *rdev , struct
       radeon_bo_va *bo_va , uint64_t soffset , uint32_t flags );

she returns an int, she takes four things, she's booked and busy πŸ’…


✨ ARGUMENTS ✨

  • rdev β€” a radeon_device pointer, aka the whole GPU device vibe check πŸ‘‘
  • bo_va β€” the bo_va that's gonna store the address. she's the one holding the receipt 🧾
  • soffset β€” the requested offset of the buffer inside the VM address space. where you want her to live, lowkey 🏑
  • flags β€” attributes of the pages, so like read/write/valid/etc. the whole personality sheet 🌈

✨ DESCRIPTION ✨

So what she actually does: she sets the offset of bo_va (cayman+ only, iykyk ✨). She validates the offset you requested and then sets it within the vm address space. Returns 0 for success, error for failure β€” classic bestie behaviour, she'll tell you if it went wrong 😭

⚠️ ok so important, do NOT skip this one β€” the object has to be reserved before you call her, and it gets unreserved by this function! so like. she takes the lock off herself. don't be weird about it. no cap πŸ™ˆ

✨ SEE ALSO ✨

the whole friend group fr fr β€” and the kernel file she lives in: ./drivers/gpu/drm/radeon/radeon_vm.c πŸ“


and that's the page, periodt πŸ’… this queen lives at ./drivers/gpu/drm/radeon, dated October 2026 β€” mwah, go reserve your object bestie, ily, bye πŸ’–πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from