[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BD261180E6D35F4D9D32F3E44FD3D901053E8543@EMPBEDEX.empirix.com>
Date: Fri, 23 Nov 2007 13:47:01 -0500
From: "Morrison, Tom" <tmorrison@...irix.com>
To: "Mark Lord" <liml@....ca>
Cc: "Robert Hancock" <hancockr@...w.ca>,
"linux-kernel" <linux-kernel@...r.kernel.org>,
"ide" <linux-ide@...r.kernel.org>, "Jeff Garzik" <jeff@...zik.org>,
"Tejun Heo" <htejun@...il.com>
Subject: RE: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)
Yes, I believe that - otherwise, this problem would have
been a crisis a LONG time ago...:-)
But I do have some more questions in relationship to how
things are mapped in your environment. I have a flat memory
map (i.e.: the full 0x0 -- 0x1_0000_0000 is passed to the 32bit
Linux kernel without any 'holes' and/or reserved areas).
Does your Intel memory map have this same type of flat memory
model (and thus allow use of the FULL lower 4Gig) - or does it
reserve areas of lower 4Gig for devices and such - if not - where
are these reserved areas - and how do the relate to the I/O memory
map for the device?
In other words, I would be very interested in seeing the memory
map & the PCI memory mapping to see if any overlap/correspond
to reserve areas of lower 4 Gig (in a linux 32bit mode)...
Tom
________________________________
From: Mark Lord [mailto:liml@....ca]
Sent: Fri 11/23/2007 12:46 PM
To: Morrison, Tom
Cc: Robert Hancock; linux-kernel; ide; Jeff Garzik; Tejun Heo
Subject: Re: [PATCH] sata_nv: fix ADMA ATAPI issues with memory over 4GB (v3)
Morrison, Tom wrote:
> I am hopeful that the sata_mv has this bug (I proved that the
> problem I was experiencing was due to the sata_mv driver
> with 3.75Gig or more of memory)...
>
> I am on vacation for a week or more ...or I'd tell you today
> if it did have this bug!
..
Yeah, I kind of had your reports in mind when I asked that. :)
On a related note, I now have lots of Marvell (sata_mv) hardware here,
and an Intel CPU/chipset box with physical RAM above the 4GB boundary.
Cheers
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists