Running work in hardware interrupt context [LWN.net]

By Jonathan Corbet
October 26, 2010

As a general rule, kernel developers work to avoid running code in hardware interrupt context; there is a whole array of mechanisms by which interrupt-driven work can be deferred to less pressing times. Apparently, however, there is an occasional need to run arbitrary code in the hardware interrupt context - and there is no hardware conveniently signaling interrupts at the time. To enable the running of code in hardware interrupt context, a new API has been added to 2.6.37.

The first step is to fill in an irq_work structure:

    #include <linux/irq_work.h>

    struct irq_work my_work;

    init_irq_work(struct irq_work *entry, void (*func)(struct irq_work *func));

There is then a fairly familiar pair of functions for running the work indicated by this structure:

    bool irq_work_queue(struct irq_work *entry);
    void irq_work_sync(struct irq_work *entry);

The intended area of use is apparently code running from non-maskable interrupts which needs to be able to interact with the rest of the system. One should assume that just about any other use of this feature is likely to be scrutinized closely.

Running work in hardware interrupt context

Posted Oct 28, 2010 8:39 UTC (Thu) by mlankhorst (subscriber, #52260) [Link] (1 responses)

Why would you want to sync work in irq context?

Running work in hardware interrupt context

Posted Oct 9, 2018 5:49 UTC (Tue) by changbin (guest, #87107) [Link]

Sometimes, you may want code be NMI safe. So you can move code from NMI context to hardirq context.