projects / linux-2.6-microblaze.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: c4484ab) | patch
dma-mapping: trace more error paths
authorSean Anderson <sean.anderson@linux.dev>
Fri, 18 Oct 2024 15:00:37 +0000 (11:00 -0400)
committerChristoph Hellwig <hch@lst.de>
Tue, 29 Oct 2024 07:54:06 +0000 (08:54 +0100)
commit68b6dbf1f441c4eba3b8511728a41cf9b01dca35
tree4eb452797a551e5c56b54374e381fafb0560acd5tree
parentc4484ab86ee00f2d9236e2851621ea02c105f4cccommit | diff
dma-mapping: trace more error paths

It can be surprising to the user if DMA functions are only traced on
success. On failure, it can be unclear what the source of the problem
is. Fix this by tracing all functions even when they fail. Cases where
we BUG/WARN are skipped, since those should be sufficiently noisy
already.

Signed-off-by: Sean Anderson <sean.anderson@linux.dev>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Signed-off-by: Christoph Hellwig <hch@lst.de>
include/trace/events/dma.h diff | blob | history
kernel/dma/mapping.c diff | blob | history
MicroBlaze GIT Repository