Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: Problems with MSI-X on ia64
Date: Tue, 21 Feb 2006 14:21:42 -0600
Message-ID: <D4CFB69C345C394284E4B78B876C1CF10BAD8CA9@cceexc23.americas.cpqcorp.net>
Thread-Topic: Problems with MSI-X on ia64
Thread-Index: AcYz/W30SdnG64fUQcK3cOXr6nYDrQDJq8ww
From: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
To: "Grundler, Grant G" <grant.grundler@hp.com>,
       "Luck, Tony" <tony.luck@intel.com>
Cc: "Chris Wedgwood" <cw@f00f.org>,
       "Grant Grundler" <grundler@parisc-linux.org>,
       "Greg KH" <gregkh@suse.de>, <linux-kernel@vger.kernel.org>,
       <linux-scsi@vger.kernel.org>, <linux-ia64@vger.kernel.org>,
       <linux-pci@atrey.karlin.mff.cuni.cz>,
       "Jesse Barnes" <jbarnes@virtuousgeek.org>,
       "Patterson, Andrew D (Linux R&D)" <andrew.patterson@hp.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 831
Lines: 25

> -----Original Message-----
> From: Grundler, Grant G 
> 
> On Fri, Feb 17, 2006 at 11:52:45AM -0800, Luck, Tony wrote:
> > > Hrm, it may be doing this.  I wonder how that works though with 
> > > 4GB's of RAM installed?
> > 
> > Systems with 4G of RAM usually map part of the RAM above 4G 
> so as to 
> > leave a hole for i/o mapping etc.
> 
> exactly.
> rx2600 physical memory map only has 1GB of RAM below 4GB 
> address space.

So I looked at 2.6.16-rc3 which works in my lab, but phys_addr is still
an int. How can that work? I believe Andrew saw the same thing in
2.6.15.

mikem
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/