NE_DEV_NAME(9)

💖 NAME 💖

Okay bestie, so this is NE_DEV_NAME(9) straight out of the Kernel API Manual, and it's literally the Nitro Enclaves (NE) misc device — the whole vibe is that it hands you the ioctl interface. That's the entire personality. Iconic, minimal, slay. ✨

✨ SYNOPSIS ✨

NE_DEV_NAME

That's it. That's the whole synopsis. No args, no flags, just the name sitting there looking pretty. 🎀

🌈 SEE ALSO 🌈

Bestie, the cross-reference list is long and honestly kind of the main character here, so buckle up 🫶

• Kernel file ./samples/nitro_enclaves/ne_ioctl_sample.c — this one's described as the sample flow of using the ioctl interface provided by the Nitro Enclaves (NE)(9). Start here if you want to see it in action fr fr.
• NE_POLL_WAIT_TIME(9)
• NE_POLL_WAIT_TIME_MS(9)
• NE_SLEEP_TIME(9)
• NE_DEFAULT_NR_VCPUS(9)
• NE_MIN_MEM_REGION_SIZE(9)
• NE_DEFAULT_NR_MEM_REGIONS(9)
• NE_IMAGE_LOAD_HEARTBEAT_CID(9)
• NE_IMAGE_LOAD_HEARTBEAT_PORT(9)
• NE_IMAGE_LOAD_HEARTBEAT_VALUE(9)
• struct ne_user_mem_region(9)
• ne_create_vm(9)
• ne_poll_enclave_fd(9)
• ne_alloc_user_mem_region(9)
• ne_load_enclave_image(9)
• ne_set_user_mem_region(9)
• ne_free_mem_regions(9)
• ne_add_vcpu(9)
• ne_start_enclave(9)
• ne_start_enclave_check_booted(9)

Go read them. All of them. Not me being a pushy bestie, I'm just saying the ioctl interface makes way more sense once you've met the whole friend group 💅

That's the whole page, bestie 💜 This little baddie lives under ./samples/nitro_enclaves and it's dated October 2026, page NE_DEV_NAME(9) — go off, you now know the lore 👑🌸