From: Christoph Hellwig Subject: Re: road blocks for using dma-iommu on more than arm64 Date: Mon, 2 Oct 2017 09:31:53 -0700 Message-ID: <20171002163153.GA17254@infradead.org> References: <20171001090245.GA22124@infradead.org> <7fcdaa8c-a12c-3264-0173-5c1be6f11ff7@arm.com> <20171002145025.GA28291@infradead.org> <7037c9c3-002b-2228-6988-aa659667056e@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <7037c9c3-002b-2228-6988-aa659667056e-5wv7dgnIgG8@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: iommu-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Robin Murphy Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org List-Id: iommu@lists.linux-foundation.org On Mon, Oct 02, 2017 at 03:56:14PM +0100, Robin Murphy wrote: > IIRC, dmabounce has to stay because it handles non-contiguous DMA masks, > thanks to a StrongARM hardware erratum where the DMA controller could > only access every other megabyte of memory (or something like that). Isn't that exactly the problem that xen-swiotlb solves?