diff options
author | Steven Rostedt <[email protected]> | 2012-11-15 11:34:21 -0500 |
---|---|---|
committer | Frederic Weisbecker <[email protected]> | 2012-11-17 19:31:03 +0100 |
commit | c0e980a4bd7fc5c9b748f2f0209d2a48c0fdf0ab (patch) | |
tree | 39eda738087b5bda53b0cb06c9549656266a03c2 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 00b42959106a9ca1c2899e591ae4e9a83ad6af05 (diff) |
irq_work: Flush work on CPU_DYING
In order not to offline a CPU with pending irq works, flush the
queue from CPU_DYING. The notifier is called by stop_machine on
the CPU that is going down. The code will not be called from irq context
(so things like get_irq_regs() wont work) but I'm not sure what the
requirements are for irq_work in that regard (Peter?). But irqs are
disabled and the CPU is about to go offline. Might as well flush the work.
Signed-off-by: Steven Rostedt <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: Ingo Molnar <[email protected]>
Cc: Andrew Morton <[email protected]>
Cc: Paul Gortmaker <[email protected]>
Signed-off-by: Frederic Weisbecker <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions