ne_setup_cpu_pool(9)
π ne_setup_cpu_pool(9) β the Kernel API Manual glow-up β¨
okay bestie, so this is ne_setup_cpu_pool(9) from the Kernel API Manual, and it's literally the bouncer at the club door for your NE CPU pool π Let's get into it.
πΈ NAME πΈ
ne_setup_cpu_pool β sets up the NE CPU pool after it's done handling all the sanity checks, and the sanity checks are not optional, they're the whole vibe fr fr. Like, it checks that you're not sharing CPU cores with the primary / parent VM (rude), and that you're not using CPU 0, because CPU 0 should stay available for the primary / parent VM π. Then, once the checks pass, it offlines the CPUs from the pool. Periodt.
β¨ SYNOPSIS β¨
int ne_setup_cpu_pool (const char *ne_cpu_list );
π¦ ARGUMENTS π¦
ne_cpu_listβ the CPU list used for setting the NE CPU pool. That's the one (1) thing you hand it, bestie π
π CONTEXT π
Process context. That's it, that's the context π
β RETURN β
0on success β slay π- Negative return value on failure β not slay π
π SEE ALSO π
Like, go read these too, they're all iconic in their own way:
- 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_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_enclave_remove_all_vcpu_id_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)
π«Ά tiny reminder for the group chat: CPU 0 stays with the primary / parent VM, no cap. Don't try it. π
and that's the page!! brought to you by ./drivers/virt/nitro_enclaves πΈ, dated October 2026, and honestly? she ate π₯ mwah π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms