gpu_buddy_a...ddr_to_block(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… 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_block on success πŸ’–
  • NULL or 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:

fr fr, go read them. iykyk πŸ”₯


kisses and good vibes from ./drivers/gpu, October 2026 πŸ’…βœ¨ mwah 🫢

πŸ“¦ where this page comes from