[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241018150036.2878190-1-sean.anderson@linux.dev>
Date: Fri, 18 Oct 2024 11:00:33 -0400
From: Sean Anderson <sean.anderson@...ux.dev>
To: Christoph Hellwig <hch@....de>,
iommu@...ts.linux.dev
Cc: Robin Murphy <robin.murphy@....com>,
linux-trace-kernel@...r.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
linux-kernel@...r.kernel.org,
Sean Anderson <sean.anderson@...ux.dev>
Subject: [PATCH v2 0/4] dma-mapping: Trace more error paths
Some DMA functions are not traced when they fail. I found this pretty
confusing, since it seems like the device skips calling the DMA function
and fails anyway. This series adds some additional tracepoints to
address this.
Changes in v2:
- Use macros to define events in a class
Sean Anderson (4):
dma-mapping: Use macros to define events in a class
dma-mapping: Trace dma_alloc/free direction
dma-mapping: Use trace_dma_alloc for dma_alloc* instead of using
trace_dma_map
dma-mapping: Trace more error paths
include/trace/events/dma.h | 213 ++++++++++++++++++++++++++++++-------
kernel/dma/mapping.c | 37 ++++---
2 files changed, 198 insertions(+), 52 deletions(-)
--
2.35.1.1320.gc452695387.dirty
Powered by blists - more mailing lists