ne_create_vm_ioctl(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ ne_create_vm_ioctl(9) β€” the Nitro Enclaves VM-creator ✨

okay so bestie, welcome to the ne_create_vm_ioctl page from the Kernel API Manual πŸ’… this is the function that allocates a slot for an enclave and hands you back a file descriptor so you can actually do stuff with it later. iconic behavior, honestly.


🌸 NAME 🌸

ne_create_vm_ioctl β€” literally allocates a slot to be associated with an enclave, and creates the enclave file descriptor that you'll use for all your enclave resource handling later (think: memory regions and CPUs, the whole vibe check) 🫢


πŸŽ€ SYNOPSIS πŸŽ€

int ne_create_vm_ioctl (struct ne_pci_dev *ne_pci_dev , u64 __user *slot_uid );

no cap, that's the whole signature right there ⭐


πŸ’– ARGUMENTS πŸ’–

  • ne_pci_dev β€” the private data associated with the PCI device. it's giving "context object" energy, she knows things πŸ‘‘
  • slot_uid β€” a user pointer where the generated unique slot id (the one associated with an enclave) gets stored. so she writes back to you, basically a little gift 🎁

πŸ¦‹ CONTEXT πŸ¦‹

Process context. This function is called with the ne_pci_dev enclave mutex held β€” so yes, the mutex is already holding court before this function even walks in. main character energy, periodt πŸ’…


πŸ”₯ RETURN πŸ”₯

  • Enclave fd on success πŸŽ‰ (a file descriptor, slay)
  • Negative return value on failure 😭 (not slay, but informative)

🌈 SEE ALSO 🌈

okay this list is a whole crew, buckle up bestie β€” the references go HARD:

like I said β€” the whole friend group πŸ’œ


okay that's the tea β˜• this page lives in ./drivers/virt/nitro_enclaves, and it's stamped October 2026 with the signature ne_create_vm_ioctl(9) β€” so if you're reading this in the future, hiiiii bestie, you're right on time βœ¨πŸŽ€πŸ’–

πŸ“¦ where this page comes from