ne_enclave_...u_id_entries(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ne_enclave_...u_id_entries(9) β€” like, the Kernel API Manual one, bestie

okay so picture this: you're deep in the kernel, the Kernel API Manual is open, and this lil' page is the one you need. it lives at ne_enclave_...u_id_entries(9) and honestly it's giving "short but essential" energy. let's go 🫢


✨ NAME ✨

ne_enclave_remove_all_vcpu_id_entries β€” literally removes all the vCPU id entries from the enclave data structure. all of them. every last one. periodt πŸ’…


🌸 SYNOPSIS 🌸

void ne_enclave_remove_all_vcpu_id_entries (struct ne_enclave
*ne_enclave );

yup, that's it β€” one argument, void return, no cap. she's simple, she's iconic, she does one job πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • ne_enclave β€” the private data that's associated with the current enclave. that's your lil' enclave bestie, the one holding all the vibes (and the data) πŸ’–

πŸ¦‹ CONTEXT πŸ¦‹

Process context. and listen β€” this function gets called with the ne_enclave mutex held. so like, don't come for her without the lock, okay?? it's giving "read the room" πŸ™ˆ

⚠️ fr fr: ne_enclave mutex held when you call this. that's not a suggestion, that's the vibe check πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

the whole friend group, all showing up to the group chat:

  • Kernel file ./drivers/virt/nitro_enclaves/ne_misc_dev.c β€” Enclave lifetime management driver for Nitro Enclaves (NE).(9)
  • NE_CPUS_SIZE(9)
  • NE_EIF_LOAD_OFFSET(9)
  • NE_MIN_ENCLAVE_MEM_SIZE(9)
  • NE_MIN_MEM_REGION_SIZE(9)
  • NE_PARENT_VM_CID(9)
  • struct ne_cpu_pool(9)
  • struct ne_phys_contig_mem_regions(9)
  • ne_check_enclaves_created(9)
  • ne_setup_cpu_pool(9)
  • ne_teardown_cpu_pool(9)
  • ne_set_kernel_param(9)
  • ne_donated_cpu(9)
  • ne_get_unused_core_from_cpu_pool(9)
  • ne_set_enclave_threads_per_core(9)
  • ne_get_cpu_from_cpu_pool(9)
  • ne_get_vcpu_core_from_cpu_pool(9)
  • ne_check_cpu_in_cpu_pool(9)
  • ne_add_vcpu_ioctl(9)
  • ne_sanity_check_user_mem_region(9)
  • ne_sanity_check_user_mem_region_page(9)
  • ne_sanity_check_phys_mem_region(9)
  • ne_merge_phys_contig_memory_regions(9)
  • ne_set_user_memory_region_ioctl(9)
  • ne_start_enclave_ioctl(9)
  • ne_enclave_ioctl(9)
  • ne_enclave_remove_all_mem_region_entries(9)
  • ne_pci_dev_remove_enclave_entry(9)
  • ne_enclave_release(9)
  • ne_enclave_poll(9)
  • ne_create_vm_ioctl(9)
  • ne_ioctl(9)

like, the whole roster. iykyk 🌈


anyway that's the page!! source/version stamp: ./drivers/virt/nitro_enclaves, dated October 2026, and she answers to ne_enclave_...u_id_entries(9) πŸ’œ

mwah πŸ’‹ go remove those vcpu id entries bestie, you got this 🧚✨

πŸ“¦ where this page comes from