From: Jun Sun <jsun@junsun.net>
To: Paul Mundt <lethal@linux-sh.org>, linux-kernel@vger.kernel.org
Subject: Re: reserve memory in low physical address - possible?
Date: Tue, 31 Oct 2006 07:06:12 -0800 [thread overview]
Message-ID: <20061031150612.GA14272@srv.junsun.net> (raw)
In-Reply-To: <20061031081239.GA9539@linux-sh.org>
On Tue, Oct 31, 2006 at 05:12:39PM +0900, Paul Mundt wrote:
> On Mon, Oct 30, 2006 at 11:22:03PM -0800, Jun Sun wrote:
> > I understand it is possible to reserve some memory at the end by
> > specifying "mem=xxxM" option in kernel command line. I looked into
> > "memmap=xxxM" option but it appears not helpful for what I want.
> >
> memmap takes multiple arguments, including the start address for the
> memory map. You could also bump min_low_pfn manually if memmap= isn't
> suitable for you, something like:
>
> magic_space = PFN_UP(init_pg_tables_end);
> min_low_pfn = magic_space + magic_size;
>
> (assuming magic_size is rounded up already), should work fine. Though
> memmap= already takes care of most of this for you, could you explain why
> it's unsuitable?
That is fair question. I got that conclusion by a quick test with
"memmap=" and kernel did not boot. :)
Now think about it, it could be because the loader (or the real-mode
part of kernel) has not been modified to deal with the initial gap.
Can someone confirm that and give some hints on how to do this?
Thanks.
Jun
next prev parent reply other threads:[~2006-10-31 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 7:22 Jun Sun
2006-10-31 8:12 ` Paul Mundt
2006-10-31 15:06 ` Jun Sun [this message]
2006-11-02 18:40 ` Jun Sun
2006-10-31 12:32 ` Richard B. Johnson
2006-10-31 15:40 ` Jun Sun
2006-10-31 16:01 ` Alan Cox
2006-10-31 12:45 ` Mark Hounschell
2006-10-31 15:14 ` Jun Sun
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=20061031150612.GA14272@srv.junsun.net \
--to=jsun@junsun.net \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
/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®