Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754992AbdL2Kw3 (ORCPT ); Fri, 29 Dec 2017 05:52:29 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:49328 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751759AbdL2Kw0 (ORCPT ); Fri, 29 Dec 2017 05:52:26 -0500 Subject: Re: consolidate direct dma mapping and swiotlb support To: Christoph Hellwig , iommu@lists.linux-foundation.org Cc: linux-mips@linux-mips.org, linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, Guan Xuetao , linux-arch@vger.kernel.org, linux-s390@vger.kernel.org, linux-c6x-dev@linux-c6x.org, linux-hexagon@vger.kernel.org, x86@kernel.org, linux-snps-arc@lists.infradead.org, adi-buildroot-devel@lists.sourceforge.net, linux-m68k@vger.kernel.org, patches@groups.riscv.org, linux-metag@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Michal Simek , linux-parisc@vger.kernel.org, linux-cris-kernel@axis.com, linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org, linuxppc-dev@lists.ozlabs.org References: <20171229081911.2802-1-hch@lst.de> From: Vladimir Murzin Message-ID: <23fee3bb-61ce-1735-b264-3acc0109c858@arm.com> Date: Fri, 29 Dec 2017 10:52:14 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20171229081911.2802-1-hch@lst.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1270 Lines: 30 On 29/12/17 08:18, Christoph Hellwig wrote: > Almost every architecture supports a direct dma mapping implementation, > where no iommu is used and the device dma address is a 1:1 mapping to > the physical address or has a simple linear offset. Currently the > code for this implementation is most duplicated over the architectures, > and the duplicated again in the swiotlb code, and then duplicated again > for special cases like the x86 memory encryption DMA ops. > > This series takes the existing very simple dma-noop dma mapping > implementation, enhances it with all the x86 features and quirks, and > creates a common set of architecture hooks for it and the swiotlb code. > > It then switches a large number of architectures to this generic > direct map implement and the new generic swiotlb dma_map ops. > > Note that for now this only handles architectures that do cache coherent > DMA, but a similar consolidation for non-coherent architectures is in the > work for later merge windows. Is it available in your dma-mapping.git or somewhere else? Cheers Vladimir > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >