ne_add_vcpu_ioctl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ne_add_vcpu_ioctl(9) πŸ’…

okay so this is the Kernel API Manual page for ne_add_vcpu_ioctl(9), and bestie it is literally about adding a vCPU to the slot associated with the current enclave. main character kernel energy, no cap ✨

✨ NAME ✨

ne_add_vcpu_ioctl β€” Add a vCPU to the slot associated with the current enclave. πŸ’–

πŸ¦‹ SYNOPSIS πŸ¦‹

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

🌸 ARGUMENTS 🌸

  • ne_enclave β€” Private data associated with the current enclave. 🫢
  • vcpu_id β€” ID of the CPU to be associated with the given slot, apic id on x86. 🧠

πŸ’… CONTEXT πŸ’…

Process context. This function is called with the ne_enclave mutex held. So when you roll up, that mutex is already in the mix β€” noted and respected, periodt. 😌

heads up bestie: process context, and the ne_enclave mutex is held when this runs. that's the whole context vibe check. πŸ’€

πŸŽ€ RETURN πŸŽ€

  • 0 β€” success. slay! βœ…
  • Negative return value β€” failure. sad girl hours, but at least it's documented 😭

πŸ‘‘ SEE ALSO πŸ‘‘

mwah πŸ’– this page's source/version is ./drivers/virt/nitro_enclaves, and it's dated October 2026 β€” see you in the group chat, bestie! πŸ§šπŸ’œ

πŸ“¦ where this page comes from