From: John Reiser <jreiser@BitWagon.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Is it possible to move Kernel Virtual Space to 0xE0000000
Date: Sat, 11 Aug 2007 08:22:47 -0700 [thread overview]
Message-ID: <46BDD447.5040903@BitWagon.com> (raw)
In-Reply-To: <f807f08a0708110414p2b9fc7c0s94dd9d10214296d5@mail.gmail.com>
> Giving Kernel virtual space to 0xD0000000 and it boots without any problems,
> however when I increase it more to 0xE0000000 it throws Program Exception. I
> will be glad if someone helps me out with refernces for Linux Porting on
> MPCs.
Search for:
linux "4G/4G split"
This work was active a couple years ago on x86. The kernel patches
are not trivial, and they cost about 15% in performance of system calls.
But they do provide almost a full 32-bits of address space for user mode.
The problem of "not enough user address space" also is solvable with
money. Get a 64-bit machine. It costs more per board but saves
development time, so costs less in the long run unless you are making
more than 10,000 systems.
--
prev parent reply other threads:[~2007-08-11 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 11:14 Is it possible to move Kernel Virtual Space to 0xE0000000 Subbu Linux
2007-08-11 15:22 ` John Reiser [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=46BDD447.5040903@BitWagon.com \
--to=jreiser@bitwagon.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).