amdgpu_doorb...get_kfd_info(9)
πΈ 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms