amdgpu_doorb...get_kfd_info(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay bestie, this is the amdgpu_doorb...get_kfd_info(9) page from the Kernel API Manual, and it's all about amdgpu_doorbell_get_kfd_info β€” reporting the doorbell configuration required to setup amdkfd. periodt. πŸ’–

✨ SYNOPSIS ✨

the signature is literally right here, untouched:

void amdgpu_doorbell_get_kfd_info (struct amdgpu_device *adev ,
phys_addr_t *aperture_base , size_t *aperture_size , size_t
*start_offset );

πŸŽ€ ARGUMENTS πŸŽ€

  • adev β€” amdgpu_device pointer, iykyk. 🫢
  • aperture_base β€” output returning doorbell aperture base physical address. ✨
  • aperture_size β€” output returning doorbell aperture size in bytes. πŸ“
  • start_offset β€” output returning # of doorbell bytes reserved for amdgpu. πŸ”₯

πŸ’… DESCRIPTION πŸ’…

so amdgpu and amdkfd share the doorbell aperture β€” it's giving shared custody, no drama. πŸ’« amdgpu sets it up, takes doorbells required for its own rings and reports the setup to amdkfd. and amdgpu reserved doorbells are at the start of the doorbell aperture, literally first in line. πŸ‘‘

πŸ¦‹ SEE ALSO πŸ¦‹

peep the kernel file ./drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c for the whole vibe. 🧚


mwah πŸ’– source/version: ./drivers/gpu/drm/amd/amdgpu Β· date: October 2026 Β· manual: amdgpu_doorb...get_kfd_info(9) β€” slay and stay curious. πŸ’…

πŸ“¦ where this page comes from