Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753444AbaKZQFA (ORCPT ); Wed, 26 Nov 2014 11:05:00 -0500 Received: from foss-mx-na.foss.arm.com ([217.140.108.86]:39856 "EHLO foss-mx-na.foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753374AbaKZQE5 (ORCPT ); Wed, 26 Nov 2014 11:04:57 -0500 Date: Wed, 26 Nov 2014 16:04:56 +0000 From: Will Deacon To: Alexander Duyck Cc: "linux-arch@vger.kernel.org" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "mathieu.desnoyers@polymtl.ca" , "peterz@infradead.org" , "benh@kernel.crashing.org" , "heiko.carstens@de.ibm.com" , "mingo@kernel.org" , "mikey@neuling.org" , "linux@arm.linux.org.uk" , "donald.c.skidmore@intel.com" , "matthew.vick@intel.com" , "geert@linux-m68k.org" , "jeffrey.t.kirsher@intel.com" , "romieu@fr.zoreil.com" , "paulmck@linux.vnet.ibm.com" , "nic_swsd@realtek.com" , "michael@ellerman.id.au" , "tony.luck@intel.com" , "torvalds@linux-foundation.org" , "oleg@redhat.com" , "schwidefsky@de.ibm.com" , "fweisbec@gmail.com" , "davem@davemloft.net" Subject: Re: [PATCH v5 2/4] arch: Add lightweight memory barriers dma_rmb() and dma_wmb() Message-ID: <20141126160456.GJ14866@arm.com> References: <20141119012205.9563.95544.stgit@ahduyck-server> <20141119012400.9563.21117.stgit@ahduyck-server> <20141125140130.GC8541@arm.com> <5474ADB4.5070200@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5474ADB4.5070200@redhat.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 25, 2014 at 04:26:28PM +0000, Alexander Duyck wrote: > On 11/25/2014 06:01 AM, Will Deacon wrote: > > If we ever see platforms using Linux/dma_alloc_coherent with devices > > mastering from a different outer-shareable domain that the one containing > > the CPUs, then we'll need to revisit this. > > Would we just need a system wide memory barrier in that case instead of > an outer shareable memory barrier, or would we need to look as something > like a sync barrier? I think dmb(sy) would do the trick, but let's cross that bridge if/when we have to. Will -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/