public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Bob Zhang <zhanglinbao@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	hayfeng Lee <omycle@gmail.com>,
	ak@linux.intel.com, Bob Zhang <2004.zhang@gmail.com>
Subject: Re: x86_64 virtual memory map
Date: Mon, 25 Jul 2011 03:33:53 -0700	[thread overview]
Message-ID: <m1ei1ewsxa.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <CAKdQVUaKea64ROeDo-SLRgQ3sHptyxD2TjKKgK5OmS+28Ee1zw@mail.gmail.com> (Bob Zhang's message of "Mon, 25 Jul 2011 18:17:05 +0800")

Bob Zhang <zhanglinbao@gmail.com> writes:

> I have HP's latest Proliant machine , The test involves using
> configurations of 1 TB of Ram then 2TB of RAM. The system ROM is
> reporting the proper amount of installed memory, however, Linux is
> only reporting 992GB with both 1TB and 2 TB of memory in the system.
> The customer has made the changes in the RMSU from 40 to 44 bit
> addressing when using the 2TB of memory but this does not change
> anything.
> I am using SLES 11 SP1 (linux kernel is 2.6.32)
> Does anyone have any idea how to get Linux to see the full amount of
> memory?

What does the e820 map printed by the kernel at the start of time
report?  In particular is all of memory visible there?

Eric


  reply	other threads:[~2011-07-25 10:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  2:20 x86_64 virtual memory map hayfeng Lee
2010-03-26  4:34 ` Eric W. Biederman
2011-07-25 10:13   ` Bob Zhang
2011-07-25 10:17     ` Bob Zhang
2011-07-25 10:33       ` Eric W. Biederman [this message]
2011-07-26  8:43         ` Bob Zhang
2011-07-26 19:26     ` Valdis.Kletnieks
2011-07-26 19:49     ` Andi Kleen
2011-07-27  7:13       ` Bob Zhang
2011-07-27 15:38         ` Andi Kleen
2011-08-19 15:13           ` Bob Zhang

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=m1ei1ewsxa.fsf@fess.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=2004.zhang@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=omycle@gmail.com \
    --cc=zhanglinbao@gmail.com \
    /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