From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from foss.arm.com (usa-sjc-mx-foss1.foss.arm.com [217.140.101.70]) by lists.ozlabs.org (Postfix) with ESMTP id 409QyX4jtqzF28F for ; Tue, 27 Mar 2018 20:41:54 +1100 (AEDT) Date: Tue, 27 Mar 2018 10:42:00 +0100 From: Will Deacon To: Arnd Bergmann Cc: Jason Gunthorpe , Benjamin Herrenschmidt , Sinan Kaya , David Laight , Oliver , "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)" , "linux-rdma@vger.kernel.org" , Alexander Duyck , "Paul E. McKenney" Subject: Re: RFC on writel and writel_relaxed Message-ID: <20180327094159.GA29373@arm.com> References: <20180326165425.GA15554@ziepe.ca> <20180326202545.GB15554@ziepe.ca> <20180326210951.GD15554@ziepe.ca> <1522101717.7364.14.camel@kernel.crashing.org> <20180326222756.GJ15554@ziepe.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, Mar 27, 2018 at 09:56:47AM +0200, Arnd Bergmann wrote: > On Tue, Mar 27, 2018 at 12:27 AM, Jason Gunthorpe wrote: > > On Tue, Mar 27, 2018 at 09:01:57AM +1100, Benjamin Herrenschmidt wrote: > >> On Mon, 2018-03-26 at 17:46 -0400, Sinan Kaya wrote: > > > > I even see patches adding wmb() based on actual observed memory > > corruption during testing on Intel: > > > > https://patchwork.kernel.org/patch/10177207/ > > > > So you think all of this is unnecessary and writel is totally strongly > > ordered, even on multi-socket Intel? > > This example adds a wmb() between two writes to a coherent DMA > area, it is definitely required there. I'm pretty sure I've never seen > any bug reports pointing to a missing wmb() between memory > and MMIO write accesses, but if you remember seeing them in the > list, maybe you can look again for some evidence of something going > wrong on x86 without it? If this is just about ordering accesses to coherent DMA, then using dma_wmb() instead will be much better performance on arm/arm64. Will