From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:47515 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S1750991AbWCHNIo (ORCPT ); Wed, 8 Mar 2006 08:08:44 -0500 Subject: Re: Memory barriers and spin_unlock safety From: Alan Cox In-Reply-To: References: <32518.1141401780@warthog.cambridge.redhat.com> <17417.29375.87604.537434@cargo.ozlabs.ibm.com> <17422.19865.635112.820824@cargo.ozlabs.ibm.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 08 Mar 2006 13:12:57 +0000 Message-Id: <1141823577.7605.31.camel@localhost.localdomain> Mime-Version: 1.0 Sender: linux-arch-owner@vger.kernel.org To: Linus Torvalds Cc: Paul Mackerras , David Howells , akpm@osdl.org, linux-arch@vger.kernel.org, bcrl@linux.intel.com, matthew@wil.cx, linux-kernel@vger.kernel.org, mingo@redhat.com, linuxppc64-dev@ozlabs.org, jblunck@suse.de List-ID: On Maw, 2006-03-07 at 19:54 -0800, Linus Torvalds wrote: > Close, yes. HOWEVER, it's only really ordered wrt the "innermost" bus. I > don't think PCI bridges are supposed to post PIO writes, but a x86 CPU > basically won't stall for them forever. The bridges I have will stall forever. You can observe this directly if an IDE device decides to hang the IORDY line on the IDE cable or you crash the GPU on an S3 card. Alan