ne_set_encl...ads_per_core(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ne_set_encl...ads_per_core(9) β€” from the Kernel API Manual bestie πŸŽ€

okay so you opened the manual page for ne_set_enclave_threads_per_core(9) and honestly? iconic of you. this is the one that sets the threads of the core you hand it, right there in the enclave data structure. let's get into it ✨


πŸ¦‹ NAME

ne_set_enclave_threads_per_core β€” sets the threads of the core you pass in, inside the enclave data structure. that's the whole vibe, no cap πŸ’–


✨ SYNOPSIS

int ne_set_enclave_threads_per_core (struct ne_enclave *ne_enclave , int
core_id , u32 vcpu_id );

look at her. returns an int, takes three things, done 🌸


🌈 ARGUMENTS

  • ne_enclave β€” the private data associated with the current enclave. like, this enclave's personal stuff 🫢
  • core_id β€” the core id you wanna grab the threads from, out of the NE CPU pool ✨
  • vcpu_id β€” the vCPU id that's part of the core you provided πŸŽ€

πŸ’œ CONTEXT

Process context, bestie πŸ’… and listen β€” this function gets called with the ne_enclave and ne_cpu_pool mutexes held. both of them. locked. so don't be out here calling it wherever, iykyk πŸ”’


πŸ”₯ RETURN

  • 0 on success πŸŽ‰
  • a negative return value on failure 😭

πŸ‘‘ SEE ALSO

Kernel file ./drivers/virt/nitro_enclaves/ne_misc_dev.c β€” the Enclave lifetime management driver for Nitro Enclaves (NE).(9), plus the whole friend group:


ngl the SEE ALSO list is giving "my entire mutuals list" and i respect it 🧚

and that's the page!! mwah πŸ’‹ this came to you from ./drivers/virt/nitro_enclaves, dated October 2026, page ne_set_encl...ads_per_core(9) β€” see you in the next one, bestie πŸ“πŸ’–

πŸ“¦ where this page comes from