public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Bodo Eggert <7eggert@gmx.de>, Andi Kleen <andi@firstfloor.org>,
	tmoore@spatial.ca, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Re: 4Gb ram not showing up
Date: Wed, 6 Jun 2007 17:55:05 -0400	[thread overview]
Message-ID: <20070606215505.GA19651@animx.eu.org> (raw)
In-Reply-To: <20070606143723.GF10008@csclub.uwaterloo.ca>

Lennart Sorensen wrote:
> On Wed, Jun 06, 2007 at 02:12:22PM +0200, Bodo Eggert wrote:
> > Change the description of CONFIG_*HIGHMEM* to reflect "lost" memory due to 
> > PCI space and the existence of the NX flag.
> > 
> > Signed-Off-By: Bodo Eggert <7eggert@gmx.de>
> > ---
> > I made this quick patch using the information from LKML as I remembered 
> > it. Please verify.
> > 
> > @@ -510,8 +510,15 @@ config NOHIGHMEM
> >  	  by the kernel to permanently map as much physical memory as
> >  	  possible.
> >  
> > -	  If the machine has between 1 and 4 Gigabytes physical RAM, then
> > +
> > +	  If the machine has between 1 and 3.5 Gigabytes physical RAM, then
> >  	  answer "4GB" here.
> > +	  

Might be better to say 3 Gigabytes instead of 3.5.  I booted a 4gb kernel on
a machine with 4gb at work and only saw 3gb of memory.

Also, I've noticed that there's ~128mb of memory lost if you select 1gb when
you have 1gb of memory installed.

> >  	  If more than 4 Gigabytes is used then answer "64GB" here. This
> >  	  selection turns Intel PAE (Physical Address Extension) mode on.
> > @@ -520,6 +527,10 @@ config NOHIGHMEM
> >  	  processors (Pentium Pro and better). NOTE: If you say "64GB" here,
> >  	  then the kernel will not boot on CPUs that don't support PAE!
> >  
> > +	  An additional benefit of the 64GB-Mode is the availability of the
> > +	  no-execute-pageflag, which can be used to prevent some attacks from
> > +	  injecting malicious code into applications.
> > +
> >  	  The actual amount of total physical memory will either be
> >  	  auto detected or can be forced by using a kernel command line option
> >  	  such as "mem=256M". (Try "man bootparam" or see the documentation of
> > @@ -532,14 +543,14 @@ config HIGHMEM4G
> >  	bool "4GB"
> >  	depends on !X86_NUMAQ
> >  	help
> > -	  Select this if you have a 32-bit processor and between 1 and 4
> > +	  Select this if you have a 32-bit processor and between 1 and 3.5
> >  	  gigabytes of physical RAM.
> >  
> >  config HIGHMEM64G
> > -	bool "64GB"
> > +	bool "64GB (enables no-execute memory protection if available)"
> >  	depends on X86_CMPXCHG64
> >  	help
> > -	  Select this if you have a 32-bit processor and more than 4
> > +	  Select this if you have a 32-bit processor and more than 3.5
> >  	  gigabytes of physical RAM.

Same here

> Seems like an improvement to me.  To fully explain how it could be 3 or
> 3.5 or 3.25 or who knows how many GB you can actually use without PAE
> would probably require writing a small novel.  Certainly talking about
> address space instead of amounts of physical memory is more correct.

It's probably worth it to just say 3gb.

I've looked at the cpuinfo for several machines, all of which (pIII and
better, not all physically support even 2gb of memory) show pae in the
flags, so is there really a reason not to just specify 64gb always?

The oldest machine I have access to is a pII 333mhz machine, cpuinfo also
lists pae in the cpu flags.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???

  reply	other threads:[~2007-06-06 21:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 12:12 [RFC][PATCH] Re: 4Gb ram not showing up Bodo Eggert
2007-06-06 14:37 ` Lennart Sorensen
2007-06-06 21:55   ` Wakko Warner [this message]
2007-06-06 22:12   ` H. Peter Anvin
2007-06-06 22:41     ` Andrew Lyon
2007-06-07 16:18       ` H. Peter Anvin
2007-06-07 17:37         ` Andrew Lyon
2007-06-09  0:47           ` H. Peter Anvin
2007-06-09 20:38           ` Matt Keenan
2007-06-07 13:49 ` Tom Moore
     [not found] <fa.KfNZpadRG0eZUXpSEPaw6ru0bsI@ifi.uio.no>
     [not found] ` <fa.onZVzrCKi+mc+cmivZh4BhVROlY@ifi.uio.no>
     [not found]   ` <fa./NQsJ0P5QQw7SMr++Q5kkRcAJHs@ifi.uio.no>
     [not found]     ` <fa.v/tV4BtD9VBbszRCBALGEBt2uUw@ifi.uio.no>
2007-06-07  0:09       ` Robert Hancock

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20070606215505.GA19651@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=7eggert@gmx.de \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=tmoore@spatial.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox