[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180508104556.GA26841@lst.de>
Date: Tue, 8 May 2018 12:45:56 +0200
From: Christoph Hellwig <hch@....de>
To: Robin Murphy <robin.murphy@....com>
Cc: Christoph Hellwig <hch@....de>, iommu@...ts.linux-foundation.org,
linux-arch@...r.kernel.org, linux-xtensa@...ux-xtensa.org,
Michal Simek <monstr@...str.eu>,
Vincent Chen <deanbo422@...il.com>,
linux-c6x-dev@...ux-c6x.org, linux-parisc@...r.kernel.org,
linux-sh@...r.kernel.org, linux-hexagon@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-m68k@...ts.linux-m68k.org,
openrisc@...ts.librecores.org, Greentime Hu <green.hu@...il.com>,
linux-alpha@...r.kernel.org, sparclinux@...r.kernel.org,
nios2-dev@...ts.rocketboards.org,
linux-snps-arc@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 3/3] dma-debug: unexport dma_debug_resize_entries and
debug_dma_dump_mappings
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.
Powered by blists - more mailing lists