amdgpu_gmc_vram_pa(9)

📦 version 7.3.1, in nixpkgs unstable

💅 amdgpu_gmc_vram_pa(9) — the Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual entry for amdgpu_gmc_vram_pa — yes that's the whole name, yes it's a mouthful, no we are not abbreviating it, it's iconic and it knows it 💖

✨ NAME ✨

amdgpu_gmc_vram_pa — literally calculates a vram buffer object's physical address from the GPU's point of view 🫶 like, not the CPU's view, the GPU's view, the main character's view, okay?? 👑

🌸 SYNOPSIS 🌸

uint64_t amdgpu_gmc_vram_pa (struct amdgpu_device *adev , struct
amdgpu_bo *bo );

it's giving "two pointer arguments in, one uint64_t out" and honestly? slay. ✨

🎀 ARGUMENTS 🎀

  • adev — an amdgpu_device pointer 💜 you know, the whole device vibe, the big one, the one that holds everything together.
  • bo — an amdgpu buffer object 🦋 the actual buffer we're out here doing address math for. no cap.

🦋 SEE ALSO 🦋

first up, the kernel file where this lives, bestie — go read the source, it's right there:

Kernel file ./drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c

and now the whole friend group 😭 the entire gmc cinematic universe:

ngl that's a whole group chat and every single one of them is invited to the function-call party 🔥

okay genuine vibe check moment: this page gives you the NAME, the SYNOPSIS, the ARGUMENTS and the SEE ALSO — that's it, that's the whole page. no DESCRIPTION, no RETURN VALUE, no ERRORS, no EXAMPLES. don't come for me, I'm not inventing lore that isn't in the source 🙈

and that's the whole page babes 💅 brought to you by ./drivers/gpu/drm/amd/amdgpu, dated October 2026 — mwah, go read amdgpu_gmc.c, ily, bye 🎀⭐🌈

📦 where this page comes from