From: Sean Anderson <sean.anderson@linux.dev>
To: Christoph Hellwig <hch@lst.de>, iommu@lists.linux.dev
Cc: Robin Murphy <robin.murphy@arm.com>,
linux-trace-kernel@vger.kernel.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org,
Sean Anderson <sean.anderson@linux.dev>
Subject: [PATCH v2 0/4] dma-mapping: Trace more error paths
Date: Fri, 18 Oct 2024 11:00:33 -0400 [thread overview]
Message-ID: <20241018150036.2878190-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.
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
next reply other threads:[~2024-10-18 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 15:00 Sean Anderson [this message]
2024-10-18 15:00 ` [PATCH v2 1/4] dma-mapping: Use macros to define events in a class Sean Anderson
2024-10-18 15:00 ` [PATCH v2 2/4] dma-mapping: Trace dma_alloc/free direction Sean Anderson
2024-10-18 15:00 ` [PATCH v2 3/4] dma-mapping: Use trace_dma_alloc for dma_alloc* instead of using trace_dma_map Sean Anderson
2024-10-25 2:19 ` Steven Rostedt
2024-10-18 15:00 ` [PATCH v2 4/4] dma-mapping: Trace more error paths Sean Anderson
2024-10-23 5:30 ` [PATCH v2 0/4] " Christoph Hellwig
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=20241018150036.2878190-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).