trim memory not covered by WB MTRRs
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Jesse Barnes
On some machines, buggy BIOSes don't properly setup WB MTRRs to cover all available RAM, meaning the last few megs (or even gigs) of memory will be marked uncached. Since Linux tends to allocate from high memory addresses first, this causes the machine to be unusably slow as soon as the kernel starts really using memory (i.e. right around init time).
Quoted 6 lines
This patch works around the problem by scanning the MTRRs at boot and figuring out whether the current
end_pfnvalue (setup by early e820 code) goes beyond the highest WB MTRR range, and if so, trimming it to match. A fairly obnoxiousKERN_WARNINGis printed too, letting the user know that not all of their memory is available due to a likely BIOS bug.
Wouldn't it be better to correct the MTRR, if possible? As far as I read here (LKML), the BIOS did not merge the entries, and this waste caused the last part of the memory not to be covered. Off cause you can't DTRT for all buggy MTRR setups, but if you're lucky, optionally merging the MTRR and adding the rest of the memory may sometimes do the trick ...
Signature · 4 lines
Funny quotes: 10. Nothing is fool proof to a talented fool. Friß, Spammer: [email protected]
Quoted 16 lines · Bodo Eggert
Quoted 7 lines · Jesse Barnes
On some machines, buggy BIOSes don't properly setup WB MTRRs to cover all available RAM, meaning the last few megs (or even gigs) of memory will be marked uncached. Since Linux tends to allocate from high memory addresses first, this causes the machine to be unusably slow as soon as the kernel starts really using memory (i.e. right around init time).
Quoted 6 lines
This patch works around the problem by scanning the MTRRs at boot and figuring out whether the current
end_pfnvalue (setup by early e820 code) goes beyond the highest WB MTRR range, and if so, trimming it to match. A fairly obnoxiousKERN_WARNINGis printed too, letting the user know that not all of their memory is available due to a likely BIOS bug.
Quoted 2 lines
Wouldn't it be better to correct the MTRR, if possible? As far as I read here (LKML), the BIOS did not merge the entries
The size/alignment constraints of MTRRs (must be a power of 2) means that the best-fit method of covering non power of 2 memory sizes is the, well.. best fit. There's nothing that can be merged.
Dave
Signature · 1 line
http://www.codemonkey.org.uk