LKML Archive on
help / color / mirror / Atom feed
From: "Diego M. Vadell" <>
To: Linux Kernel <>
Subject: PAT and MTRRs
Date: Sun, 26 Oct 2008 22:46:21 -0100	[thread overview]
Message-ID: <> (raw)


   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."


             reply	other threads:[~2008-10-27  0:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-26 23:46 Diego M. Vadell [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \
    --subject='Re: PAT and MTRRs' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).