STRUCT NE_ENCLAVE_START_INFO(9)

✨ NAME ✨

struct ne_enclave_start_info — the little setup-info struct you need for enclave start, and it's in / out bestie, meaning it's both an input AND an output, she's versatile 💅

okay so real talk, this page lives in the Kernel API Manual, section 9, and it's about one tiny struct that carries the tea the hypervisor needs before your enclave can ~start~ ✨

🦋 SYNOPSIS 🦋

struct ne_enclave_start_info {
    __u64 flags;
    __u64 enclave_cid;
 };

that's it. two fields. lowkey iconic for how much she does with so little 🎀

🌸 Members 🌸

• flags — the flags your enclave starts with (think debug mode and friends) — this one is (in) only, so you're the one filling it out 🫶
• enclave_cid — the Context ID (CID) for the enclave's vsock device. and here's the cute part: if you pass in 0 as input, the CID gets autogenerated by the hypervisor and handed right back to you as output by the driver. she's (in / out) — you give her something, she maybe gives you something better ✨

btw the whole struct is described as (in / out) up in the NAME section, so don't let the input-only flags field confuse you — the struct as a whole does the round trip 💖

💅 SEE ALSO 💅

the whole friend group, fr fr — go read these next:

• ./include/uapi/linux/nitro_enclaves.h
• Nitro Enclaves (NE) Kernel Driver Interface(9)
• NE_CREATE_VM(9)
• NE_ADD_VCPU(9)
• NE_GET_IMAGE_LOAD_INFO(9)
• NE_SET_USER_MEMORY_REGION(9)
• NE_START_ENCLAVE(9)
• NE specific error codes(9)
• NE_ERR_VCPU_ALREADY_USED(9)
• NE_ERR_VCPU_NOT_IN_CPU_POOL(9)
• NE_ERR_VCPU_INVALID_CPU_CORE(9)
• NE_ERR_INVALID_MEM_REGION_SIZE(9)
• NE_ERR_INVALID_MEM_REGION_ADDR(9)
• NE_ERR_UNALIGNED_MEM_REGION_ADDR(9)
• NE_ERR_MEM_REGION_ALREADY_USED(9)
• NE_ERR_MEM_NOT_HUGE_PAGE(9)
• NE_ERR_MEM_DIFFERENT_NUMA_NODE(9)
• NE_ERR_MEM_MAX_REGIONS(9)
• NE_ERR_NO_MEM_REGIONS_ADDED(9)
• NE_ERR_NO_VCPUS_ADDED(9)
• NE_ERR_ENCLAVE_MEM_MIN_SIZE(9)
• NE_ERR_FULL_CORES_NOT_USED(9)
• NE_ERR_NOT_IN_INIT_STATE(9)
• NE_ERR_INVALID_VCPU(9)
• NE_ERR_NO_CPUS_AVAIL_IN_POOL(9)
• NE_ERR_INVALID_PAGE_SIZE(9)
• NE_ERR_INVALID_FLAG_VALUE(9)
• NE_ERR_INVALID_ENCLAVE_CID(9)
• Image load info flags(9)
• NE_EIF_IMAGE(9)
• struct ne_image_load_info(9)
• User memory region flags(9)
• NE_DEFAULT_MEMORY_REGION(9)
• struct ne_user_memory_region(9)
• Enclave start info flags(9)
• NE_ENCLAVE_PRODUCTION_MODE(9)
• NE_ENCLAVE_DEBUG_MODE(9)

and that's the whole page, bestie 🧚 no cap, every field and every cross-reference accounted for. this one was sourced from ./include/uapi/linux and dated October 2026 — go off, you're basically a kernel dev now 👑💜