From: Sean Anderson <sean.anderson@linux.dev>
To: Christoph Hellwig <hch@lst.de>, iommu@lists.linux.dev
Cc: linux-trace-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, Robin Murphy <robin.murphy@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Steven Rostedt <rostedt@goodmis.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Sean Anderson <sean.anderson@linux.dev>
Subject: [PATCH 0/3] dma-mapping: Trace more error paths
Date: Thu, 17 Oct 2024 14:13:51 -0400 [thread overview]
Message-ID: <20241017181354.2834674-1-sean.anderson@linux.dev> (raw)
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.
Sean Anderson (3):
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 | 161 +++++++++++++++++++++++++++++++++++--
kernel/dma/mapping.c | 37 ++++++---
2 files changed, 178 insertions(+), 20 deletions(-)
--
2.35.1.1320.gc452695387.dirty
next reply other threads:[~2024-10-17 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 18:13 Sean Anderson [this message]
2024-10-17 18:13 ` [PATCH 1/3] dma-mapping: Trace dma_alloc/free direction Sean Anderson
2024-10-17 18:13 ` [PATCH 2/3] dma-mapping: Use trace_dma_alloc for dma_alloc* instead of using trace_dma_map Sean Anderson
2024-10-18 5:27 ` Christoph Hellwig
2024-10-17 18:13 ` [PATCH 3/3] dma-mapping: Trace more error paths Sean Anderson
2024-10-21 10:38 ` Robin Murphy
2024-10-21 14:37 ` Sean Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241017181354.2834674-1-sean.anderson@linux.dev \
--to=sean.anderson@linux.dev \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).