From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Christoph Hellwig <hch@lst.de>,
iommu@lists.linux-foundation.org, linux-arch@vger.kernel.org,
linux-xtensa@linux-xtensa.org, Michal Simek <monstr@monstr.eu>,
Vincent Chen <deanbo422@gmail.com>,
linux-c6x-dev@linux-c6x.org, linux-parisc@vger.kernel.org,
linux-sh@vger.kernel.org, linux-hexagon@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
openrisc@lists.librecores.org, Greentime Hu <green.hu@gmail.com>,
linux-alpha@vger.kernel.org, sparclinux@vger.kernel.org,
nios2-dev@lists.rocketboards.org,
linux-snps-arc@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] dma-debug: unexport dma_debug_resize_entries and debug_dma_dump_mappings
Date: Tue, 8 May 2018 12:45:56 +0200 [thread overview]
Message-ID: <20180508104556.GA26841@lst.de> (raw)
In-Reply-To: <bb5bb25f-24da-9729-a39b-3b88c65ef628@arm.com>
On Tue, May 08, 2018 at 11:05:20AM +0100, Robin Murphy wrote:
> On 24/04/18 15:02, Christoph Hellwig wrote:
>> Only used by the AMD GART driver, which must be built in.
>
> FWIW debug_dma_dump_mappings() is also called by the Intel VT-d driver, but
> the same reasoning still applies.
I'll update the changelog.
> This does rather beg the question of
> whether it's right to have bits of low-level dma-debug internals *only*
> called by a couple of IOMMU drivers, but that can wait for another day.
My gut feeling is that it is wrong, but I didn't have time to look into
the details and history of how this happened.
next prev parent reply other threads:[~2018-05-08 10:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 14:02 dma-debug cleanups, including removing the arch hook Christoph Hellwig
2018-04-24 14:02 ` Christoph Hellwig
[not found] ` <20180424140235.9125-1-hch-jcswGhMUV9g@public.gmane.org>
2018-04-24 14:02 ` [PATCH 1/3] dma-debug: move initialization to common code Christoph Hellwig
2018-04-24 14:02 ` Christoph Hellwig
[not found] ` <20180424140235.9125-2-hch-jcswGhMUV9g@public.gmane.org>
2018-05-08 9:46 ` Robin Murphy
2018-05-08 9:46 ` Robin Murphy
2018-05-08 10:22 ` Marek Szyprowski
2018-05-08 10:22 ` Marek Szyprowski
2018-04-24 14:02 ` [PATCH 3/3] dma-debug: unexport dma_debug_resize_entries and debug_dma_dump_mappings Christoph Hellwig
2018-04-24 14:02 ` Christoph Hellwig
[not found] ` <20180424140235.9125-4-hch-jcswGhMUV9g@public.gmane.org>
2018-05-08 10:05 ` Robin Murphy
2018-05-08 10:05 ` Robin Murphy
2018-05-08 10:45 ` Christoph Hellwig [this message]
2018-05-08 10:45 ` Christoph Hellwig
2018-04-27 15:53 ` [PATCH 4/3] dma-debug: remove CONFIG_HAVE_DMA_API_DEBUG Christoph Hellwig
2018-04-27 15:53 ` Christoph Hellwig
[not found] ` <20180427155342.GA9232-jcswGhMUV9g@public.gmane.org>
2018-05-08 9:54 ` Robin Murphy
2018-05-08 9:54 ` Robin Murphy
2018-05-07 10:29 ` dma-debug cleanups, including removing the arch hook Christoph Hellwig
2018-05-07 10:29 ` Christoph Hellwig
2018-04-24 14:02 ` [PATCH 2/3] dma-debug: simplify counting of preallocated requests Christoph Hellwig
2018-04-24 14:02 ` Christoph Hellwig
[not found] ` <20180424140235.9125-3-hch-jcswGhMUV9g@public.gmane.org>
2018-05-08 9:50 ` Robin Murphy
2018-05-08 9:50 ` Robin Murphy
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=20180508104556.GA26841@lst.de \
--to=hch@lst.de \
--cc=deanbo422@gmail.com \
--cc=green.hu@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=monstr@monstr.eu \
--cc=nios2-dev@lists.rocketboards.org \
--cc=openrisc@lists.librecores.org \
--cc=robin.murphy@arm.com \
--cc=sparclinux@vger.kernel.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).