From: Ingo Molnar <mingo@elte.hu>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: Zhao Forrest <forrest.zhao@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
discuss@x86-64.org, linux-kernel@vger.kernel.org,
yhlu.kernel@gmail.com, ak@suse.de
Subject: Re: Does Linux have plan to support memory hole remapping?
Date: Wed, 9 Apr 2008 10:54:40 +0200 [thread overview]
Message-ID: <20080409085440.GB32466@elte.hu> (raw)
In-Reply-To: <20080409083700.GU3700@mea-ext.zmailer.org>
* Matti Aarnio <matti.aarnio@zmailer.org> wrote:
> On Wed, Apr 09, 2008 at 10:01:59AM +0200, Andi Kleen wrote:
> > "Zhao Forrest" <forrest.zhao@gmail.com> writes:
> > >
> > > As we can see from above information that the physical memory in system
> > > is 32768MB(32GB). However OS is only using about
> > > (32768-512)MB(MemTotal: 33010240 kB). Does this mean that this
> > > linux kernel can't use the physical memory remapped
> > > from (4G-512M, 4G) to (32G, 32G+512M)?
> >
> > The linux kernel can only use the memory passed to it by the BIOS.
> > Sometimes they need special BIOS setup options to enable remapping. If
> > there are no such options and you can't upgrade it you're out of luck
> >
> > I would suggest you contact your system vendor.
>
> I second that. On my home machine I have early ASUS AMD x64 board
> from a few years ago. For it I did buy CPU with this memory mapping
> hardware inside, but the BIOS did not support it correctly until a
> year or two latter, thus I was not able to use all of 4 GB of memory I
> had installed there. There was support in BIOS from start, but it did
> things wrong.
having said that - but we'll still consider sane looking patches that
allow the remapping of otherwise inactive RAM. [ We might not even have
to touch the system chipset beyond what Linux already knows about it: in
theory someone might want to try a hack to GART remap such RAM areas and
use a sparse mem map entry to map it to Linux - if the identity of that
RAM is crystal-clear and there's enough GART space available. But even
then it's probably still at best a dangerous and fragile hack. ]
Ingo
next prev parent reply other threads:[~2008-04-09 8:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 7:54 Zhao Forrest
2008-04-09 8:01 ` Andi Kleen
2008-04-09 8:37 ` Matti Aarnio
2008-04-09 8:49 ` Andi Kleen
2008-04-09 8:54 ` Ingo Molnar [this message]
2008-04-09 9:03 ` Andi Kleen
2008-04-10 0:34 ` Kasper Sandberg
2008-04-10 2:09 ` H. Peter Anvin
2008-04-10 12:41 ` Kasper Sandberg
2008-04-10 6:51 ` Andi Kleen
2008-04-09 9:04 ` Zhao Forrest
2008-04-09 9:13 ` Andi Kleen
2008-04-10 6:51 ` Zhao Forrest
2008-04-10 7:22 ` Andi Kleen
2008-04-09 9:50 ` Arne Georg Gleditsch
2008-04-09 10:03 ` Andi Kleen
2008-04-09 10:16 ` Arne Georg Gleditsch
2008-04-09 18:02 ` Yinghai Lu
2008-04-09 13:34 ` Lennart Sorensen
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=20080409085440.GB32466@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=andi@firstfloor.org \
--cc=discuss@x86-64.org \
--cc=forrest.zhao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=yhlu.kernel@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
all inboxes | Powered by JetHome®