ENUM NE_PCI_DEV_CMD_TYPE(9)

🌸 enum ne_pci_dev_cmd_type — a Kernel API Manual moment 💅

okay so bestie, we're looking at enum ne_pci_dev_cmd_type from the Kernel API Manual, and honestly? it's giving "backstage pass to how the Nitro Enclaves PCI device talks to the kernel." every single command type lives in here, so let's go through them one by one, no skips, no cap 🎀

---

✨ NAME ✨

enum ne_pci_dev_cmd_type — the device command types. that's it, that's the whole vibe. every command the device can receive is chillin' in this one enum like a little roster 👑

---

🦋 SYNOPSIS 🦋

enum ne_pci_dev_cmd_type {
    INVALID_CMD ,
    ENCLAVE_START ,
    ENCLAVE_GET_SLOT ,
    ENCLAVE_STOP ,
    SLOT_ALLOC ,
    SLOT_FREE ,
    SLOT_ADD_MEM ,
    SLOT_ADD_VCPU ,
    SLOT_COUNT ,
    NEXT_SLOT ,
    SLOT_INFO ,
    SLOT_ADD_BULK_VCPUS ,
    MAX_CMD

};

lowkey a whole lineup, right? okay, now the lore behind each one 🌈

---

💖 Constants 💖

• INVALID_CMD — the invalid command. it's the "this is not a real thing" entry, the placeholder of the group chat 🙈
• ENCLAVE_START — starts an enclave, after you've set its resources. resources first, then start — order matters, bestie, don't come for me 💅
• ENCLAVE_GET_SLOT — gets the slot uid of an enclave. it's giving "who's your slot bestie" 🪪
• ENCLAVE_STOP — terminates an enclave. dramatic but necessary 💀
• SLOT_ALLOC — allocates a slot for an enclave. securing the spot ✨
• SLOT_FREE — frees the slot allocated for an enclave. closure, periodt 🦋
• SLOT_ADD_MEM — adds a memory region to an enclave slot. memory room service 🧚
• SLOT_ADD_VCPU — adds a vCPU to an enclave slot. one (1) vCPU, hand-delivered 🎀
• SLOT_COUNT — gets the number of allocated slots. the headcount 👑
• NEXT_SLOT — gets the next slot in the list of allocated slots. scrolling to the next one ➡️
• SLOT_INFO — gets the info for a slot, e.g. slot uid, vCPUs count. the full profile, iykyk 🔥
• SLOT_ADD_BULK_VCPUS — adds a number of vCPUs, not providing CPU ids. bulk mode, no ids needed, iconic ⭐
• MAX_CMD — a gatekeeper for the max possible command type. it's literally just standing there holding the door 👯

---

🫶 SEE ALSO 🫶

okay so the kernel file for all this is ./drivers/virt/nitro_enclaves/ne_pci_dev.h, and the whole extended friend group is here — go say hi:

• Nitro Enclaves (NE) PCI device(9)
• PCI_DEVICE_ID_NE(9)
• PCI_BAR_NE(9)
• Device registers in the NE PCI device MMIO BAR(9)
• NE_ENABLE(9)
• NE_VERSION(9)
• NE_COMMAND(9)
• NE_EVTCNT(9)
• NE_SEND_DATA(9)
• NE_RECV_DATA(9)
• Device MMIO buffer sizes(9)
• NE_SEND_DATA_SIZE(9)
• NE_RECV_DATA_SIZE(9)
• MSI-X interrupt vectors(9)
• NE_VEC_REPLY(9)
• NE_VEC_EVENT(9)
• Device commands - payload structure for requests and replies.(9)
• struct enclave_start_req(9)
• struct enclave_get_slot_req(9)
• struct enclave_stop_req(9)
• struct slot_alloc_req(9)
• struct slot_free_req(9)
• struct slot_add_mem_req(9)
• struct slot_add_vcpu_req(9)
• struct slot_count_req(9)
• struct next_slot_req(9)
• struct slot_info_req(9)
• struct slot_add_bulk_vcpus_req(9)
• struct ne_pci_dev_cmd_reply(9)
• struct ne_pci_dev(9)
• ne_do_request(9)

---

ngl if you're messing with these, read the friends too — the req/reply structs match up with the commands above, and that's the whole point 🧚

---

that's the page, bestie!! it lives at ./drivers/virt/nitro_enclaves, and this lil slice of documentation is dated October 2026 — enum ne_pci_dev_cmd_type(9), slaying in a man page near you 💜✨