amdgpu_device_mm_access(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… amdgpu_device_mm_access β€” access vram by MM_INDEX/MM_DATA ✨

okay so bestie, welcome to the amdgpu_device_mm_access(9) page from the Kernel API Manual 🫢 this one is literally all about poking at vram through MM_INDEX/MM_DATA, and we're gonna get you comfy with it, no cap.


🌸 SYNOPSIS 🌸

void amdgpu_device_mm_access (struct amdgpu_device *adev , loff_t pos ,
       void *buf , size_t size , bool write );

✨ ARGUMENTS ✨

  • adev β€” an amdgpu_device pointer πŸ’– like, the GPU we're talking to, periodt.
  • pos β€” offset of the buffer in vram πŸŽ€ it's giving "where in vram are we hanging out today".
  • buf β€” virtual address of the buffer in system memory πŸ¦‹ the system-side buddy for the data.
  • size β€” read/write size, and heads up bestie: sizeof(buf) must > size 🌈 don't fumble this one, fr fr.
  • write β€” true means write to vram, otherwise it's read from vram πŸ’… simple as that iykyk.

πŸ‘‘ SEE ALSO πŸ‘‘

the kernel file is literally living at ./drivers/gpu/drm/amd/amdgpu/amdgpu_device.c πŸ“‚ and here's the whole squad of related pages β€” obsessed with how many there are, honestly:


aaaaand that's the whole page, bestie πŸŽ€ this cutie came from ./drivers/gpu/drm/amd/amdgpu in the October 2026 edition of the Kernel API Manual, mwah πŸ’– go forth and slay your vram access πŸ’…βœ¨

πŸ“¦ where this page comes from