amdgpu_vm_bo_map(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

amdgpu_vm_bo_map β€” map bo inside a vm.

Okay bestie, this is the amdgpu_vm_bo_map(9) page from the Kernel API Manual, and it’s giving β€œkernel mapping but make it cute” ✨

🌸 SYNOPSIS 🌸

int amdgpu_vm_bo_map (struct amdgpu_device *adev , struct amdgpu_bo_va
*bo_va , uint64_t saddr , uint64_t offset , uint64_t size , uint32_t
flags );

πŸŽ€ ARGUMENTS πŸŽ€

  • adev β€” amdgpu_device pointer. The device vibe check πŸ‘‘
  • bo_va β€” bo_va to store the address.
  • saddr β€” where to map the BO.
  • offset β€” requested offset in the BO.
  • size β€” BO size in bytes.
  • flags β€” attributes of pages (read/write/valid/etc.). Basically the page’s personality settings πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

Adds a mapping of the BO at the specefied addr into the VM.

🚨 Object has to be reserved and unreserved outside! This call is not out here doing that for you, bestie. Handle it outside, okay? 🫢

πŸ”₯ RETURN πŸ”₯

  • 0 for success β€” slay βœ…
  • error for failure β€” not slay, but at least it tells you 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c, plus the whole linked squad:


Cute lil sign-off: this page lives under ./drivers/gpu/drm/amd/amdgpu, dated October 2026, and it’s still amdgpu_vm_bo_map(9) from the Kernel API Manual. Bye bestie! πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from