handle_fasteoi_nmi(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ handle_fasteoi_nmi(9) ✨

okay so bestie, we're in the Kernel API Manual and this page is literally about the irq handler for NMI interrupt lines. It's giving low-level kernel realness, and we're gonna get through it together. πŸ’–

🌸 NAME 🌸

handle_fasteoi_nmi β€” irq handler for NMI interrupt lines.

πŸ¦‹ SYNOPSIS πŸ¦‹

void handle_fasteoi_nmi (struct irq_desc *desc );

πŸŽ€ ARGUMENTS πŸŽ€

  • desc β€” the interrupt description structure for this irq. Yes bestie, that's the whole argument, and it's iconic.

πŸ’… DESCRIPTION πŸ’…

okay so picture this: handle_fasteoi_nmi is a simple NMI-safe handler, and it's out here considering the restrictions from request_nmi. No cap.

The way it works is: only a single callback will be issued to the chip β€” an ->eoi call when the interrupt has been serviced. That's it. One callback, one vibe. 🫢

This enables support for modern forms of interrupt handlers, which handle the flow details in hardware, transparently. Like, the hardware is doing the flow stuff, and this handler is just showing up to do its one little ->eoi moment. Slay. ✨

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./kernel/irq/chip.c


okay bye bestie 🫢 this page is from the Kernel API Manual; its source/version footer is ./kernel/irq, the date is October 2026, and the page title is handle_fasteoi_nmi(9). periodt. πŸ’œ

πŸ“¦ where this page comes from