ne_get_cpu_from_cpu_pool(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ne_get_cpu_from_cpu_pool(9) β€” the Kernel API Manual glow-up πŸŽ€

okay so bestie, welcome to the Kernel API Manual page for ne_get_cpu_from_cpu_pool β€” yes the name is a mouthful, yes it's iconic, no we are not shortening it πŸ’–


✨ NAME ✨

ne_get_cpu_from_cpu_pool β€” grab a CPU out of the NE CPU pool. and like… from where exactly? two options, queen: either it's one of the remaining sibling(s) of a CPU core, or it's the first sibling of a new CPU core. that's the whole vibe check πŸ¦‹


🌸 SYNOPSIS 🌸

int ne_get_cpu_from_cpu_pool (struct ne_enclave *ne_enclave , u32
*vcpu_id );

literally that's it. two args. slay ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • ne_enclave β€” the private data associated with the current enclave. it's giving "personal info, do not share" 🫢
  • vcpu_id β€” the vCPU that we're getting from the NE CPU pool. main character vCPU fr πŸ’…

πŸ¦‹ CONTEXT πŸ¦‹

Process context, bestie. and listen β€” this function is called with the ne_enclave mutex held. so like, hold the lock, don't be weird about it πŸ™ˆ


⭐ RETURN ⭐

  • 0 on success πŸŽ‰ (we love a zero)
  • Negative return value on failure 😭 (we do NOT love a negative, but it happens)

πŸ‘‘ SEE ALSO πŸ‘‘

the whole friend group, no cap β€” every single one of these:

like, read them. all of them. iykyk πŸ”₯


and that's the page, bestie πŸ§šπŸ’œ this lil masterpiece lives under ./drivers/virt/nitro_enclaves and it's stamped October 2026 β€” frame it, hang it up, periodt πŸ’…πŸŒΈ

πŸ“¦ where this page comes from