From: Kasper Sandberg <lkml@metanurb.dk>
To: Ingo Molnar <mingo@elte.hu>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
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: Thu, 10 Apr 2008 02:34:47 +0200 [thread overview]
Message-ID: <1207787687.30698.97.camel@localhost> (raw)
In-Reply-To: <20080409085440.GB32466@elte.hu>
On Wed, 2008-04-09 at 10:54 +0200, Ingo Molnar wrote:
[..]
>
> 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
A somewhat related question is.. How come linux does not(as i understand
it) support talking to the chipsets to do these things? wouldnt this
also give other benefits, such as being able to more precisely control
interrupts and stuff?
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2008-04-10 0:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 7:54 Does Linux have plan to support memory hole remapping? 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
2008-04-09 9:03 ` Andi Kleen
2008-04-10 0:34 ` Kasper Sandberg [this message]
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=1207787687.30698.97.camel@localhost \
--to=lkml@metanurb.dk \
--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=mingo@elte.hu \
--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