public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Haim D." <haimdaniel@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: x86_32 machine with 4G - possible wrong last_pfn value ?
Date: Sun, 06 Mar 2011 12:11:23 -0800	[thread overview]
Message-ID: <4D73EA6B.1050002@zytor.com> (raw)
In-Reply-To: <AANLkTi=H8uOpqC56GCt9U89nDWChG5nQa4kUz+fxHPdc@mail.gmail.com>

On 03/06/2011 07:04 AM, Haim D. wrote:
> Hi,
> I'm running  a x86_32 bit 4G machine with 2.4.33 and 2.6.34, I've
> noticed the difference between max_pfn values
> 2.4.33 shows 0x100000
> 2.4.34 shows  0xdffe0
> 

[ ... ]

> Mar  6 13:27:17 localhost kernel: BIOS-provided physical RAM map:
> Mar  6 13:27:17 localhost kernel:  BIOS-e820: 0000000000000000 -
> 000000000009fc00 (usable)
> Mar  6 13:27:17 localhost kernel:  BIOS-e820: 000000000009fc00 -
> 00000000000a0000 (reserved)
> Mar  6 13:27:17 localhost kernel:  BIOS-e820: 00000000000e0000 -
> 0000000000100000 (reserved)
> Mar  6 13:27:17 localhost kernel:  BIOS-e820: 0000000000100000 -
> 00000000dffe0000 (usable)
> Mar  6 13:27:17 localhost kernel:  BIOS-e820: 00000000dffe0000 -
> 00000000dffee000 (ACPI data)
> Mar  6 13:27:17 localhost kernel:  BIOS-e820: 00000000dffee000 -
> 00000000e0000000 (ACPI NVS)
> Mar  6 13:27:17 localhost kernel:  BIOS-e820: 00000000fee00000 -
> 00000000fee01000 (reserved)
> Mar  6 13:27:17 localhost kernel:  BIOS-e820: 00000000ffb00000 -
> 0000000100000000 (reserved)
> Mar  6 13:27:17 localhost kernel:  BIOS-e820: 0000000100000000 -
> 0000000120000000 (usable)

Based on this memory map, 0xdffe0 is the correct max_pfn value.

> Mar  6 13:27:17 localhost kernel: Warning only 4GB will be used.
> Mar  6 13:27:17 localhost kernel: Use a PAE enabled kernel.
> Mar  6 13:27:17 localhost kernel: (find_max_low_pfn:1003) max_low_pfn to 753664
> Mar  6 13:27:17 localhost kernel: 1152MB HIGHMEM available.
> Mar  6 13:27:17 localhost kernel: 2944MB LOWMEM available.

... for a non-PAE kernel, apparently compiled with a weird split.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


      reply	other threads:[~2011-03-06 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=BszM8mwQ+Ooff+8D1vOXZ1=LLOp3MwPcPQu4-@mail.gmail.com>
2011-03-06 15:04 ` x86_32 machine with 4G - possible wrong last_pfn value ? Haim D.
2011-03-06 20:11   ` H. Peter Anvin [this message]

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=4D73EA6B.1050002@zytor.com \
    --to=hpa@zytor.com \
    --cc=haimdaniel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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