panthor_heap_pool_create(9)

📦 version 7.3.1, in nixpkgs unstable

💜 panthor_heap_pool_create(9) — the Kernel API Manual, bestie edition 🎀

okay so you're in the kernel API manual (section 9, iykyk) and the function we're obsessing over today is literally called panthor_heap_pool_create. yes she's a mouthful, no we're not renaming her, periodt. ✨

🌸 NAME 🌸

panthor_heap_pool_create — Create a heap pool. that's it, that's the whole job, and she does it gorgeously 💅

🦋 SYNOPSIS 🦋

struct panthor_heap_pool * panthor_heap_pool_create (struct
panthor_device *ptdev , struct panthor_vm *vm );

like, she takes two things and hands you back a struct panthor_heap_pool *. main character energy fr fr 👑

🎀 ARGUMENTS 🎀

  • ptdev — the Device. your actual hardware babe, the thing doing the work 💖
  • vm — the VM this heap pool will be attached to. yes she's ride-or-die with exactly one VM, no cap 🫶

⭐ DESCRIPTION ⭐

so here's the vibe: heap pools might contain up to 128 heap contexts (one hundred and twenty-eight, iconic number, no notes), and they're per-VM. meaning every VM gets its own pool, they don't share, they don't pass things around, that's the whole arrangement 🧚

🌈 RETURN 🌈

  • a valid pointer on success — slay 💅
  • a negative error code otherwise — 😭 not slay, but at least it's informative

🔥 SEE ALSO 🔥

the kernel file ./drivers/gpu/drm/panthor/panthor_heap.c is where all the lore lives, bestie, go read it. and also these absolute icons:

ngl if you skip the SEE ALSO list the heaps will simply not vibe with you. read them all. it's giving "required reading" for a reason 💀

that's the whole page, bestie — straight from ./drivers/gpu/drm/panthor, dated October 2026, signed off as panthor_heap_pool_create(9) and honestly? she ate. 🍓✨ bye ilysm 🫶💜

📦 where this page comes from