ne_reply_handler(9)

💖 ne_reply_handler(9) 💖

okay so bestie, we're in the Kernel API Manual today and the vibe is interrupts. This is ne_reply_handler — the interrupt handler that goes and grabs a reply when it matches up with a request you sent to the PCI device for enclave lifetime management. iykyk, it's giving matchmaker energy: request goes out, reply comes back, and this little icon makes the introduction 🎀

---

✨ SYNOPSIS ✨

irqreturn_t ne_reply_handler (int irq , void *args );

literally the whole signature. no notes. slay.

---

🌸 ARGUMENTS 🌸

• irq — the interrupt that just showed up, representing a reply the PCI device sent back to you. it's the doorbell ringing, basically 🔔
• args — the PCI device's private data structure. yes it's void *, no we don't make the rules, we just pass it through 🫶

---

🦋 CONTEXT 🦋

interrupt context. like, interrupt context interrupt context. keep it quick in there, bestie — no sleeping, no nonsense, just handle it and go 💅

---

👑 RETURN 👑

• IRQ_HANDLED when the interrupt has been handled. that's it, that's the whole list, and honestly? iconic ⭐

---

💜 SEE ALSO 💜

• the kernel file ./drivers/virt/nitro_enclaves/ne_pci_dev.c — Nitro Enclaves (NE) PCI device driver.(9)
• NE_DEFAULT_TIMEOUT_MSECS(9)
• ne_submit_request(9)
• ne_retrieve_reply(9)
• ne_wait_for_reply(9)
• ne_event_work_handler(9)
• ne_event_handler(9)
• ne_setup_msix(9)
• ne_teardown_msix(9)
• ne_pci_dev_enable(9)
• ne_pci_dev_disable(9)
• ne_pci_probe(9)
• ne_pci_remove(9)
• ne_pci_shutdown(9)

like, read the whole friend group, they all hang out together fr fr 🌈

---

ngl this one's short but it's important — if you're poking at the Nitro Enclaves PCI driver, this handler is part of how requests and replies find each other. don't skip it 🙈

---

mwah, that's a wrap 💋 this page lives in ./drivers/virt/nitro_enclaves, dated October 2026, and it goes by ne_reply_handler(9) — periodt. 🌸🦋✨