xe_guc_buf_gpu_addr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ xe_guc_buf_gpu_addr ✨

okay so bestie, welcome to the kernel API manual for xe_guc_buf_gpu_addr β€” this is a section 9 page from the Kernel API Manual, and honestly? it's a whole little vibe. it's short, it's sweet, it does exactly one thing, and it does it slayfully πŸ’…


🌸 NAME 🌸

xe_guc_buf_gpu_addr β€” bestie, this one just obtains a GPU address of the sub-allocation. that's it. that's the whole personality. iconic behavior honestly πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

u64 xe_guc_buf_gpu_addr (const struct xe_guc_buf buf );

yes that's the entire signature, no cap β€” it hands you back a u64, and it takes a const struct xe_guc_buf named buf. clean. minimal. main character energy ✨


πŸ“ ARGUMENTS πŸ“

  • buf β€” the xe_guc_buf to query πŸ’– like, this is the thing you're asking about, girl. you hand it over and it's gonna tell you where it lives on the GPU.

πŸ”₯ RETURN πŸ”₯

it returns a GPU address of the sub-allocation. periodt. no complicated multi-value situation, no -errno dramatics described here β€” just the address, straight up 🫢

ngl this page is tiny but that doesn't mean you skip the details, okay? a GPU address is a GPU address, and you need it 🌈

🌈 SEE ALSO 🌈

so here's the group chat of related functions, and yes you should absolutely go read them too, iykyk πŸ‘‘


🧚 sign-off 🧚

this lil masterpiece lives in ./drivers/gpu/drm/xe, and it's dated October 2026 β€” that's the source/version and date from the footer, mwah πŸ’œ go forth and query your GPU addresses, bestie, you're literally gonna ate this πŸŽ€β­πŸ’…

πŸ“¦ where this page comes from