panthor_heap_grow(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… panthor_heap_grow(9) β€” like, the Kernel API Manual page, bestie πŸŽ€

okay so real talk, this is a page from the Kernel API Manual and it's all about panthor_heap_grow β€” the little function whose whole entire job is to make a heap context grow. that's it. that's the vibe. main character energy fr fr ✨


🌸 NAME 🌸

panthor_heap_grow β€” Make a heap context grow.

like literally the name says it. we're growing a heap context. slay πŸ’…


✨ SYNOPSIS ✨

int panthor_heap_grow (struct panthor_heap_pool *pool , u64 heap_gpu_va
, u32 renderpasses_in_flight , u32 pending_frag_count , u64
*new_chunk_gpu_va );

no cap, that's the whole signature. it returns an int and takes five things. we'll get into each one, don't worry 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

okay bestie, here's the cast of characters, and each one matters:

  • pool β€” The pool this heap belongs to. it's giving "your heap's home base," iykyk 🏠
  • heap_gpu_va β€” The GPU address of the heap context. that's the u64 address situation, very GPU, very address ✨
  • renderpasses_in_flight β€” Number of render passes currently in-flight. like, how many are literally airborne right now πŸ›«
  • pending_frag_count β€” Number of fragment jobs waiting for execution/completion. they're in the queue, being patient, we love them for it 😭
  • new_chunk_gpu_va β€” Pointer used to return the chunk VA. it's an out-param, so it hands the chunk VA back to you 🎁

πŸ”₯ RETURN πŸ”₯

the return values, and yes we're listing all three because facts are facts:

  • 0 if a new heap was allocated β€” a win, we ate, no crumbs πŸ‘‘
  • -ENOMEM if the tiler context reached the maximum number of chunks or if too many render passes are in-flight or if the allocation failed β€” yeah that's three separate ways to hit it, all one error code, that's just how it is πŸ’€
  • -EINVAL if any of the arguments passed to panthor_heap_grow is invalid β€” bad input, invalid vibes, blocked πŸ™ˆ

🌈 SEE ALSO 🌈

here's the whole friend group, all of them, in order, no one left behind:


bestie reminder: -ENOMEM shows up for three whole reasons (max chunks reached, too many render passes in-flight, or the allocation straight-up failing) β€” don't forget any of them, okay? πŸ’–

and that's the page!! source lives at ./drivers/gpu/drm/panthor, dated October 2026, and it's the panthor_heap_grow(9) page πŸ¦‹βœ¨ mwah, go grow that heap, ily πŸ«ΆπŸ’œ

πŸ“¦ where this page comes from