From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Tue, 03 Oct 2017 13:43:51 +0200 (CEST) Received: from verein.lst.de ([213.95.11.211]:33056 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S23993156AbdJCLng4o4HQ (ORCPT ); Tue, 3 Oct 2017 13:43:36 +0200 Received: by newverein.lst.de (Postfix, from userid 2407) id C909568CEE; Tue, 3 Oct 2017 13:43:30 +0200 (CEST) Date: Tue, 3 Oct 2017 13:43:30 +0200 From: Christoph Hellwig To: Christophe LEROY Cc: Christoph Hellwig , iommu@lists.linux-foundation.org, Chris Zankel , Michal Simek , linux-ia64@vger.kernel.org, linux-mips@linux-mips.org, linux-sh@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-xtensa@linux-xtensa.org, x86@kernel.org, linux-kernel@vger.kernel.org, David Howells , Max Filippov , Guan Xuetao , Robin Murphy , Marek Szyprowski Subject: Re: [PATCH 07/11] powerpc: make dma_cache_sync a no-op Message-ID: <20171003114330.GA24592@lst.de> References: <20171003104311.10058-1-hch@lst.de> <20171003104311.10058-8-hch@lst.de> <670a0571-1a36-51a3-db52-64bc61184c35@c-s.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <670a0571-1a36-51a3-db52-64bc61184c35@c-s.fr> User-Agent: Mutt/1.5.17 (2007-11-01) Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 60235 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: hch@lst.de Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On Tue, Oct 03, 2017 at 01:24:57PM +0200, Christophe LEROY wrote: >> powerpc does not implement DMA_ATTR_NON_CONSISTENT allocations, so it >> doesn't make any sense to do any work in dma_cache_sync given that it >> must be a no-op when dma_alloc_attrs returns coherent memory. > What about arch/powerpc/mm/dma-noncoherent.c ? > > Powerpc 8xx doesn't have coherent memory. It doesn't implement the DMA_ATTR_NON_CONSISTENT interface either, so if it really doesn't have a way to provide dma coherent allocation (although the code in __dma_alloc_coherent suggests it does provide dma coherent allocations) I have no idea how it could ever have worked.