From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: MMIO and gcc re-ordering issue Date: Wed, 28 May 2008 07:12:46 +1000 Message-ID: <1211922766.3286.84.camel@pasglop> References: <1211852026.3286.36.camel@pasglop> <20080526.184047.88207142.davem@davemloft.net> <1211854540.3286.42.camel@pasglop> <20080526.192812.184590464.davem@davemloft.net> <1211859542.3286.46.camel@pasglop> Reply-To: benh@kernel.crashing.org Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from gate.crashing.org ([63.228.1.57]:35136 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757301AbYE0VNJ (ORCPT ); Tue, 27 May 2008 17:13:09 -0400 In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: Linus Torvalds Cc: David Miller , linux-arch@vger.kernel.org, scottwood@freescale.com, linuxppc-dev@ozlabs.org, alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org, tpiepho@freescale.com On Tue, 2008-05-27 at 09:47 -0700, Linus Torvalds wrote: > > __read[bwlq]()/__write[bwlq]() are not serialized with a :"memory" > barrier, although since they still use "asm volatile" I suspect that > i > practice they are probably serial too. Did not look very closely at > any > generated code (only did a trivial test to see that the code looks > *roughly* correct). Nah, asm volatile doesn't help, it does need the "memory" clobber too. Cheers, Ben.