amdgpu_bo_ge...erred_domain(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME

ok so this is amdgpu_bo_ge...erred_domain(9) from the Kernel API Manual, and bestie, the whole personality of this page is literally just: amdgpu_bo_get_preferred_domain — get preferred domain. that's it. that's the vibe. short king energy 👑

✨ SYNOPSIS ✨

uint32_t amdgpu_bo_get_preferred_domain (struct amdgpu_device *adev ,
uint32_t domain );

lowkey the cleanest signature ever — you hand it a device and a domain mask, you get back a uint32_t, no drama 🎀

🌸 ARGUMENTS 🌸

  • adev — the amdgpu device object 🖥️ like, the actual GPU you're talking about
  • domain — the allowed memory domains, i.e. the memory domains <amdgpu_memory_domains> ref. think of it as the menu of places the buffer could live, and this is the list of what's on the menu 🍓

🦋 RETURN 🦋

it tells you which of the allowed domains is the preferred one for allocating the BO. so like, out of everything you said was legal, which one does the kernel actually want? that one. slay 💅✨

ngl the return value is only as good as the domain mask you feed it — the allowed domains are exactly what you passed in, no cap.

🔥 SEE ALSO 🔥

the kernel file is right here, go read it:

./drivers/gpu/drm/amd/amdgpu/amdgpu_object.c

and here's the whole friend group (yes, all of them, i'm not skipping anyone, that would be rude 🙈):

ok that's the whole page, go allocate something iconic 💜🫶

./drivers/gpu/drm/amd/amdgpu · October 2026 · amdgpu_bo_ge...erred_domain(9) — mwah, that's a wrap, stream it, cite it, love it 🌈⭐

📦 where this page comes from