gpu_buddy_a...ddr_to_block(9)
π gpu_buddy_a...ddr_to_block(9) β like, the Kernel API Manual page, bestie β¨
okay so picture this: you're deep in the kernel API manual (section 9, the real one), and you've got a relative address and a dream. this page is gpu_buddy_allocated_addr_to_block, and it's literally the function that goes "bestie, which allocated block does this address belong to?" π
β¨ NAME β¨
gpu_buddy_allocated_addr_to_block β given a relative address, find the allocated block π¦
like. that's the whole job. hand it an address, get the block back. no cap.
πΈ SYNOPSIS πΈ
struct gpu_buddy_block * gpu_buddy_allocated_addr_to_block (struct gpu_buddy *mm , u64 addr );
that signature is iconic and we're not touching a single character of it π
π«Ά ARGUMENTS π«Ά
mmβ the GPU buddy manager. your main character, honestly πaddrβ the relative address. yes, relative. that's the vibe check it has to pass π
β RETURN β
- a
gpu_buddy_blockon success π NULLor an error code on failure π
ngl, bestie β always check it. NULL does not text back and neither do error codes. π
π§ SEE ALSO π§
kernel file ./drivers/gpu/buddy.c, and the whole friend group:
gpu_buddy_assert(9)gpu_buddy_init(9)gpu_buddy_fini(9)gpu_buddy_reset_clear(9)gpu_buddy_free_block(9)gpu_buddy_free_list(9)gpu_buddy_block_trim(9)gpu_buddy_alloc_blocks(9)gpu_buddy_block_print(9)gpu_buddy_print(9)
fr fr, go read them. iykyk π₯
kisses and good vibes from ./drivers/gpu, October 2026 π
β¨ mwah π«Ά
π¦ 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