From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org ([63.228.1.57]:12191 "EHLO gate.crashing.org") by vger.kernel.org with ESMTP id S267469AbUIPFA3 (ORCPT ); Thu, 16 Sep 2004 01:00:29 -0400 Subject: Re: RFC: being more anal about iospace accesses.. From: Benjamin Herrenschmidt In-Reply-To: <1095310669.5109.4.camel@gaston> References: <1095287935.1688.4.camel@mulgrave> <20040916023325.GJ642@parcelfarce.linux.theplanet.co.uk> <1095310669.5109.4.camel@gaston> Content-Type: text/plain Message-Id: <1095310731.5107.6.camel@gaston> Mime-Version: 1.0 Date: Thu, 16 Sep 2004 14:58:52 +1000 Content-Transfer-Encoding: 7bit To: Linus Torvalds Cc: Matthew Wilcox , James Bottomley , Geert Uytterhoeven , Linux Arch list , Al Viro , Andrew Morton , Alan Cox , "David S. Miller" , Jeff Garzik List-ID: On Thu, 2004-09-16 at 14:57, Benjamin Herrenschmidt wrote: > On Thu, 2004-09-16 at 14:28, Linus Torvalds wrote: > > > (Note that 64-bit accesses aren't necessarily atomic even on 64-bit > > architectures. BenH says that the IO architecture on a G5 means that when > > you do a 64-bit load, it will be done as two 32-bit bus cycles > > regardless). > > Yup, at least with the current models, due to the fact that the U3 > northbridge basically has a 32 bits path to IO devices. Note that this > isn't the case with IBM machines who do proper 64 bits PCI IOs. Hrm... now I'm confused ... it _MIGHT_ be able to do 64 bits wide IOs in fact ... but it's limited to 32 bits _addresses_ ... oh well... Ben.