LKML Archive on
help / color / mirror / Atom feed
* PAT and MTRRs
@ 2008-10-26 23:46 Diego M. Vadell
  2008-10-27  0:12 ` Arjan van de Ven
  2008-10-27  5:17 ` Yinghai Lu
  0 siblings, 2 replies; 10+ messages in thread
From: Diego M. Vadell @ 2008-10-26 23:46 UTC (permalink / raw)
  To: Linux Kernel


   I have 6 identical PCs (HPC cluster) with MTRR problems. In older kernels, 
I had to use "mem=3300M", or else, I would get a very slowly boot (as when 
you run out of MTRRs). 

   So I thought that PAT would make this lack of MTRRs problem go away, and 
upgraded to and, but it didn't: I still get (from dmesg)

x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 704MB of RAM.

   Most probably, I understood wrong. I read's article [1] about PAT 
several times, Documentation/x86/pat.txt , tried to use mtrr_chunk_size= and 
mtrr_gran_size= in various combinations (as discussed in this LKML thread 
[2]), but I still don't get it.

   So, what did I miss? Am I wrong thinking that PAT is a better MTRR (wrt 
setting the cache type of the RAM)? 

Thanks in advance,
 -- Diego.

"The PAT bits are more flexible and, since they live in the page table 
entries, they are difficult to run out of. They are also completely under the 
control of the operating system instead of the BIOS."


^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2008-11-11 14:30 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-10-26 23:46 PAT and MTRRs Diego M. Vadell
2008-10-27  0:12 ` Arjan van de Ven
2008-10-27  0:21   ` H. Peter Anvin
2008-10-27  0:34     ` Arjan van de Ven
2008-10-27  0:38       ` H. Peter Anvin
2008-10-27  5:17 ` Yinghai Lu
2008-10-31 22:42   ` Diego M. Vadell
2008-10-31 23:19     ` Yinghai Lu
2008-10-31 23:35     ` Yinghai Lu
2008-11-11 14:30       ` Diego M. Vadell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).