From: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
To: hch-jcswGhMUV9g@public.gmane.org
Cc: cai-0UDz38MK/Mo@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: [PATCH 0/4] dma-debug: implement dynamic entry allocation
Date: Mon, 3 Dec 2018 17:28:05 +0000 [thread overview]
Message-ID: <cover.1543856576.git.robin.murphy@arm.com> (raw)
The HNS_ENET discussion got me thinking, why not just make DMA debug
cleverer so that (in terms of basic functionality at least) we don't
need to worry about driver- or arch-specific configuration at all?
Patches #2 and #3 are the real meat here - #1 is just some preparatory
cleanup motivated by moving printks around, and could be split out if
desired; I kept #4 separate as a possible nice-to-have depending on
what people think.
Robin.
Robin Murphy (4):
dma-debug: Use pr_fmt()
dma-debug: Refactor dma_debug_entry allocation
dma-debug: Dynamically expand the dma_debug_entry pool
dma-debug: Make leak-like behaviour apparent
kernel/dma/debug.c | 198 ++++++++++++++++++++++++---------------------
1 file changed, 105 insertions(+), 93 deletions(-)
--
2.19.1.dirty
WARNING: multiple messages have this Message-ID (diff)
From: Robin Murphy <robin.murphy@arm.com>
To: hch@lst.de
Cc: m.szyprowski@samsung.com, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, cai@gmx.us, salil.mehta@huawei.com,
john.garry@huawei.com
Subject: [PATCH 0/4] dma-debug: implement dynamic entry allocation
Date: Mon, 3 Dec 2018 17:28:05 +0000 [thread overview]
Message-ID: <cover.1543856576.git.robin.murphy@arm.com> (raw)
The HNS_ENET discussion got me thinking, why not just make DMA debug
cleverer so that (in terms of basic functionality at least) we don't
need to worry about driver- or arch-specific configuration at all?
Patches #2 and #3 are the real meat here - #1 is just some preparatory
cleanup motivated by moving printks around, and could be split out if
desired; I kept #4 separate as a possible nice-to-have depending on
what people think.
Robin.
Robin Murphy (4):
dma-debug: Use pr_fmt()
dma-debug: Refactor dma_debug_entry allocation
dma-debug: Dynamically expand the dma_debug_entry pool
dma-debug: Make leak-like behaviour apparent
kernel/dma/debug.c | 198 ++++++++++++++++++++++++---------------------
1 file changed, 105 insertions(+), 93 deletions(-)
--
2.19.1.dirty
next reply other threads:[~2018-12-03 17:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 17:28 Robin Murphy [this message]
2018-12-03 17:28 ` [PATCH 0/4] dma-debug: implement dynamic entry allocation Robin Murphy
2018-12-03 17:28 ` [PATCH 1/4] dma-debug: Use pr_fmt() Robin Murphy
2018-12-04 14:26 ` Christoph Hellwig
2018-12-04 17:35 ` Joe Perches
2018-12-03 17:28 ` [PATCH 2/4] dma-debug: Refactor dma_debug_entry allocation Robin Murphy
2018-12-04 14:27 ` Christoph Hellwig
[not found] ` <20181204142731.GB2767-jcswGhMUV9g@public.gmane.org>
2018-12-04 16:09 ` Robin Murphy
2018-12-04 16:09 ` Robin Murphy
2018-12-03 17:28 ` [PATCH 3/4] dma-debug: Dynamically expand the dma_debug_entry pool Robin Murphy
2018-12-03 18:23 ` John Garry
2018-12-03 18:23 ` John Garry
2018-12-04 13:11 ` Robin Murphy
2018-12-04 14:17 ` Christoph Hellwig
2018-12-04 16:06 ` Robin Murphy
2018-12-04 16:30 ` John Garry
2018-12-04 16:30 ` John Garry
2018-12-04 17:19 ` Robin Murphy
2018-12-04 17:38 ` John Garry
2018-12-04 17:38 ` John Garry
2018-12-04 14:29 ` Christoph Hellwig
[not found] ` <20181204142938.GC2767-jcswGhMUV9g@public.gmane.org>
2018-12-04 16:32 ` Robin Murphy
2018-12-04 16:32 ` Robin Murphy
2018-12-03 17:28 ` [RFC 4/4] dma-debug: Make leak-like behaviour apparent Robin Murphy
[not found] ` <7ec928f0bd92122f271c421e99aaeb593ccabdf5.1543856576.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2018-12-04 14:31 ` Christoph Hellwig
2018-12-04 14:31 ` Christoph Hellwig
2018-12-03 17:34 ` [PATCH 0/4] dma-debug: implement dynamic entry allocation 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=cover.1543856576.git.robin.murphy@arm.com \
--to=robin.murphy-5wv7dgnigg8@public.gmane.org \
--cc=cai-0UDz38MK/Mo@public.gmane.org \
--cc=hch-jcswGhMUV9g@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.