From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: MMIO and gcc re-ordering issue Date: Tue, 03 Jun 2008 07:53:24 +1000 Message-ID: <1212443604.26672.7.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> <20080602103643.GA21285@elte.hu> 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]:46423 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751292AbYFBVyc (ORCPT ); Mon, 2 Jun 2008 17:54:32 -0400 In-Reply-To: <20080602103643.GA21285@elte.hu> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Ingo Molnar Cc: Linus Torvalds , 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 Mon, 2008-06-02 at 12:36 +0200, Ingo Molnar wrote: > The patch passed initial light testing in -tip (~30 successful random > self-builds and bootups on various mixed 32-bit/64-bit boxes) but > it's > still v2.6.27 material IMO. I think adding the "memory" clobber should be .26 and even -stable. We know for sure newer gcc will re-order things, we know it for sure some drivers will break in subtle ways because of that, ad we know as well that sticking "memory" clobber in there will fix that breakage we know about ... So I don't see the point of waiting. Ben.