aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/task-analyzer.py
diff options
context:
space:
mode:
authorDave Jiang <dave.jiang@intel.com>2023-04-07 13:31:28 -0700
committerVinod Koul <vkoul@kernel.org>2023-04-12 23:18:44 +0530
commit0c40bfb4c2dfad00a15337bb6213f92a797e3695 (patch)
treed6537ecd8c441e12c8496143322b1a434b299c63 /tools/perf/scripts/python/task-analyzer.py
parentc9566127f021c891e14c937b1b711874b7880e48 (diff)
downloadlinux-0c40bfb4c2dfad00a15337bb6213f92a797e3695.tar.gz
linux-0c40bfb4c2dfad00a15337bb6213f92a797e3695.tar.bz2
linux-0c40bfb4c2dfad00a15337bb6213f92a797e3695.zip
dmaengine: idxd: make misc interrupt one shot
Current code continuously processes the interrupt as long as the hardware is setting the status bit. There's no reason to do that since the threaded handler will get called again if another interrupt is asserted. Also through testing, it has shown that if a misprogrammed (or malicious) agent can continuously submit descriptors with bad completion record and causes errors to be reported via the misc interrupt. Continuous processing by the thread can cause software hang watchdog to kick off since the thread isn't giving up the CPU. Reported-by: Sanjay Kumar <sanjay.k.kumar@intel.com> Tested-by: Tony Zhu <tony.zhu@intel.com> Signed-off-by: Dave Jiang <dave.jiang@intel.com> Co-developed-by: Fenghua Yu <fenghua.yu@intel.com> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com> Link: https://lore.kernel.org/r/20230407203143.2189681-2-fenghua.yu@intel.com Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions