Re: Does Linux have plan to support memory hole remapping?

[Arne Georg Gleditsch]

Andi Kleen <andi@xxxxxxxxxxxxxx> writes:
> On Wed, Apr 09, 2008 at 11:50:00AM +0200, Arne Georg Gleditsch wrote:
>> Hm, wouldn't the given e820 map and mtrr listing indicate that 512M were
>> actually remapped to 32G+ in this case?
>
> The way it usually works (if it is implemented correctly in the BIOS) 
> is that all memory starting at the hole moves up together 
> (often subject to DIMM boundaries etc.),
> not that the area below the hole is remapped individually.

Yes, bad choice of words on my part.

> BTW it is not actually 512MB that is lost. MemTotal does not 
> include mem_map and that alone is ~512MB (64 bytes for each 4K page)
>
> So as far as I can see there is no missing memory remapping in Zhao's case, 
> he's just confused by the MemTotal semantics.

...meaning that upgrading his BIOS isn't going to change anything for
him, which is what I suspected from the e820 readouts.

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