mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-27 06:34:11 +08:00
e360adbe29
Provide a mechanism that allows running code in IRQ context. It is most useful for NMI code that needs to interact with the rest of the system -- like wakeup a task to drain buffers. Perf currently has such a mechanism, so extract that and provide it as a generic feature, independent of perf so that others may also benefit. The IRQ context callback is generated through self-IPIs where possible, or on architectures like powerpc the decrementer (the built-in timer facility) is set to generate an interrupt immediately. Architectures that don't have anything like this get to do with a callback from the timer tick. These architectures can call irq_work_run() at the tail of any IRQ handlers that might enqueue such work (like the perf IRQ handler) to avoid undue latencies in processing the work. Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Acked-by: Kyle McMartin <kyle@mcmartin.ca> Acked-by: Martin Schwidefsky <schwidefsky@de.ibm.com> [ various fixes ] Signed-off-by: Huang Ying <ying.huang@intel.com> LKML-Reference: <1287036094.7768.291.camel@yhuang-dev> Signed-off-by: Ingo Molnar <mingo@elte.hu>
21 lines
416 B
C
21 lines
416 B
C
#ifndef _LINUX_IRQ_WORK_H
|
|
#define _LINUX_IRQ_WORK_H
|
|
|
|
struct irq_work {
|
|
struct irq_work *next;
|
|
void (*func)(struct irq_work *);
|
|
};
|
|
|
|
static inline
|
|
void init_irq_work(struct irq_work *entry, void (*func)(struct irq_work *))
|
|
{
|
|
entry->next = NULL;
|
|
entry->func = func;
|
|
}
|
|
|
|
bool irq_work_queue(struct irq_work *entry);
|
|
void irq_work_run(void);
|
|
void irq_work_sync(struct irq_work *entry);
|
|
|
|
#endif /* _LINUX_IRQ_WORK_H */
|