DEVICE COMMANDS - PAYLOAD STRUCTURE FOR REQUESTS AND REPLIES.(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🧚 Device comm...and replies. β€” Kernel API Manual, section (9)

okay so bestie, real talk: the title up top literally reads Device comm...and replies.(9) β€” yes, it's cut off mid-word, and no, we are not fixing it. That's just how it lives in the Kernel API Manual, and it's a section 9 page. Iconic behavior, honestly. πŸŽ€

And what's it about? One line, one vibe: device commands β€” payload structure for requests and replies. That's the whole thing. It's your cheat sheet for how the request/reply payloads get shaped. That's it, that's the page. 🫢


🌸 SEE ALSO 🌸

bestie this page is basically a SEE ALSO β€” it's giving "my job here is to point you at the real main characters." So here's the full crew, in order, no skips, no cap. πŸ‘‘

πŸ“ the kernel file

  • the kernel file ./drivers/virt/nitro_enclaves/ne_pci_dev.h β€” the source of truth, the whole reason we're here πŸ’–

πŸ¦‹ the device, its registers, and its commands

  • 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)

πŸ“ the MMIO buffer sizes

  • Device MMIO buffer sizes(9)
  • NE_SEND_DATA_SIZE(9)
  • NE_RECV_DATA_SIZE(9)

✨ the MSI-X interrupt vectors

  • MSI-X interrupt vectors(9)
  • NE_VEC_REPLY(9)
  • NE_VEC_EVENT(9)

πŸ’… the structs and the function (the actual payload players)

  • enum ne_pci_dev_cmd_type(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)
🌈 that's the list, and yes, you're gonna want to read basically all of them β€” each one is a different little envelope for a request or a reply, and this page is just the girl standing at the door telling you who's who. no cap, go click through them.

and that's the whole page, bestie β€” short, sweet, absolutely serving as a directory and nothing more. πŸ’œ

sign-off time πŸŽ€ this one lives under ./drivers/virt/nitro_enclaves, it's stamped October 2026, and the footer still calls itself Device comm...and replies.(9) β€” truncated title and all, and we love her for it. periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from