STRUCT ENCLAVE_START_REQ(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct enclave_start_req(9) πŸ’–

okay bestie, so this is a page straight out of the Kernel API Manual β€” it's all about struct enclave_start_req, and ngl it's giving "the little form you fill out to wake an enclave up" energy. 🫢


✨ NAME ✨

struct enclave_start_req β€” the ENCLAVE_START request. periodt, that's the whole vibe. πŸŽ€


🌸 SYNOPSIS 🌸

here's the actual shape of it, copy it exactly bestie:

struct enclave_start_req {
    u64 slot_uid;
    u64 enclave_cid;
    u64 flags;
 };

three fields, all u64, no cap. πŸ’…


πŸ¦‹ Members πŸ¦‹

  • slot_uid β€” the slot's unique id, mapped to the enclave you're starting. literally the "which one" field. πŸ”₯
  • enclave_cid β€” the Context ID (CID) for the enclave's vsock device. and here's the cute part: if it's 0, the CID gets autogenerated for you. no thoughts, it just happens. ✨
  • flags β€” the flags the enclave starts with (e.g. debug mode). yes bestie, debug mode is a flag, go off. πŸ›

πŸ‘‘ SEE ALSO πŸ‘‘

okay this is the long part and i'm not skipping a single one, because every link here ate and left no crumbs. all of these live in the kernel file ./drivers/virt/nitro_enclaves/ne_pci_dev.h πŸ’œ:

like, the whole friend group showed up. iconique. 🌈


and that's the page!! mwah πŸ’‹ this lil beauty ships from ./drivers/virt/nitro_enclaves and it's dated October 2026 β€” so yeah, future-coded bestie, mark your calendar πŸ—“οΈβœ¨πŸ’–

πŸ“¦ where this page comes from