Commit 1ab991dc authored by Sebastian Andrzej Siewior's avatar Sebastian Andrzej Siewior
Browse files

irq_work: Allow irq_work_sync() to sleep if irq_work() no IRQ support.

irq_work() triggers instantly an interrupt if supported by the
architecture. Otherwise the work will be processed on the next timer
tick. In worst case irq_work_sync() could spin up to a jiffy.

irq_work_sync() is usually used in tear down context which is fully
preemptible. Based on review irq_work_sync() is invoked from preemptible
context and there is one waiter at a time. This qualifies it to use
rcuwait for synchronisation.

Let irq_work_sync() synchornize with rcuwait if the architecture
processes irqwork via the timer tick.
Signed-off-by: default avatarSebastian Andrzej Siewior <>
parent 14eb7712
......@@ -3,6 +3,7 @@
#include <linux/smp_types.h>
#include <linux/rcuwait.h>
* An entry can be in one of four states:
......@@ -16,11 +17,13 @@
struct irq_work {
struct __call_single_node node;
void (*func)(struct irq_work *);
struct rcuwait irqwait;
#define __IRQ_WORK_INIT(_func, _flags) (struct irq_work){ \
.node = { .u_flags = (_flags), }, \
.func = (_func), \
.irqwait = __RCUWAIT_INITIALIZER(irqwait), \
#define IRQ_WORK_INIT(_func) __IRQ_WORK_INIT(_func, 0)
......@@ -181,6 +181,9 @@ void irq_work_single(void *arg)
* else claimed it meanwhile.
(void)atomic_cmpxchg(&work->node.a_flags, flags, flags & ~IRQ_WORK_BUSY);
if (!arch_irq_work_has_interrupt())
static void irq_work_run_list(struct llist_head *list)
......@@ -247,6 +250,13 @@ void irq_work_tick_soft(void)
void irq_work_sync(struct irq_work *work)
if (!arch_irq_work_has_interrupt()) {
rcuwait_wait_event(&work->irqwait, !irq_work_is_busy(work),
while (irq_work_is_busy(work))
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment