diff options
author | Dan Williams <[email protected]> | 2014-02-19 16:19:35 -0800 |
---|---|---|
committer | Dan Williams <[email protected]> | 2014-02-25 09:44:20 -0800 |
commit | da87ca4d4ca101f177fffd84f1f0a5e4c0343557 (patch) | |
tree | 5b2be4209f11af7a3df5cf68997e9547612481ef /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace | |
parent | 6d0abeca3242a88cab8232e4acd7e2bf088f3bc2 (diff) |
ioat: fix tasklet tear down
Since commit 77873803363c "net_dma: mark broken" we no longer pin dma
engines active for the network-receive-offload use case. As a result
the ->free_chan_resources() that occurs after the driver self test no
longer has a NET_DMA induced ->alloc_chan_resources() to back it up. A
late firing irq can lead to ksoftirqd spinning indefinitely due to the
tasklet_disable() performed by ->free_chan_resources(). Only
->alloc_chan_resources() can clear this condition in affected kernels.
This problem has been present since commit 3e037454bcfa "I/OAT: Add
support for MSI and MSI-X" in 2.6.24, but is now exposed. Given the
NET_DMA use case is deprecated we can revisit moving the driver to use
threaded irqs. For now, just tear down the irq and tasklet properly by:
1/ Disable the irq from triggering the tasklet
2/ Disable the irq from re-arming
3/ Flush inflight interrupts
4/ Flush the timer
5/ Flush inflight tasklets
References:
https://lkml.org/lkml/2014/1/27/282
https://lkml.org/lkml/2014/2/19/672
Cc: Ingo Molnar <[email protected]>
Cc: Steven Rostedt <[email protected]>
Cc: <[email protected]>
Reported-by: Mike Galbraith <[email protected]>
Reported-by: Stanislav Fomichev <[email protected]>
Tested-by: Mike Galbraith <[email protected]>
Tested-by: Stanislav Fomichev <[email protected]>
Reviewed-by: Thomas Gleixner <[email protected]>
Signed-off-by: Dan Williams <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace')
0 files changed, 0 insertions, 0 deletions