RE: Problems with MSI-X on ia64
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: "Grundler, Grant G" <grant.grundler@xxxxxx>, "Luck, Tony" <tony.luck@xxxxxxxxx>
- Subject: RE: Problems with MSI-X on ia64
- From: "Miller, Mike (OS Dev)" <Mike.Miller@xxxxxx>
- Date: Tue, 21 Feb 2006 14:21:42 -0600
- Cc: "Chris Wedgwood" <cw@xxxxxxxx>, "Grant Grundler" <grundler@xxxxxxxxxxxxxxxx>, "Greg KH" <gregkh@xxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>, <linux-scsi@xxxxxxxxxxxxxxx>, <linux-ia64@xxxxxxxxxxxxxxx>, <linux-pci@xxxxxxxxxxxxxxxxxxxxxxxx>, "Jesse Barnes" <jbarnes@xxxxxxxxxxxxxxxx>, "Patterson, Andrew D (Linux R&D)" <andrew.patterson@xxxxxx>
- Thread-index: AcYz/W30SdnG64fUQcK3cOXr6nYDrQDJq8ww
- Thread-topic: Problems with MSI-X on ia64
> -----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
-
: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]