NE_COMMAND(9)

💅 NE_COMMAND(9) — the write-only command-request register 💅

Okay so bestie, welcome to the Kernel API Manual page for NE_COMMAND(9). This one is short, sweet, and honestly kind of iconic: it's the little register that tells the device what command was requested. ✨

🎀 NAME 🎀

NE_COMMAND — a (4 bytes) register to notify the device what command was requested (Write-Only). Yep, write-only, so don't come here looking to read it back like it's a text from your ex. 💀

✨ SYNOPSIS ✨

NE_COMMAND

That's the whole synopsis. Minimalist queen behavior, no cap. 👑

🌈 SEE ALSO 🌈

The whole friend group is here, so go say hi:

• Kernel file ./drivers/virt/nitro_enclaves/ne_pci_dev.h
• 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_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)
• enum ne_pci_dev_cmd_type(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)

Signed, sealed, delivered from ./drivers/virt/nitro_enclaves, dated October 2026, manual NE_COMMAND(9) — mwah 💋🫶