From: "Subbu Linux" <subbu.linux@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Is it possible to move Kernel Virtual Space to 0xE0000000
Date: Sat, 11 Aug 2007 16:44:28 +0530 [thread overview]
Message-ID: <f807f08a0708110414p2b9fc7c0s94dd9d10214296d5@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
Hello PPCTeam,
I would like to know whether I can move kernel virtual space to 0xE0000000
from 0xC0000000, if so can someone suggest me what are the pros and cons, I
know moving kernel is not good idea since Non Linux Standard, but then I
need to expand user space as one of my applications uses huge mmap space.
I tried so far
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.
Regards
Subbu
[-- Attachment #2: Type: text/html, Size: 672 bytes --]
next reply other threads:[~2007-08-11 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 11:14 Subbu Linux [this message]
2007-08-11 15:22 ` Is it possible to move Kernel Virtual Space to 0xE0000000 John Reiser
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=f807f08a0708110414p2b9fc7c0s94dd9d10214296d5@mail.gmail.com \
--to=subbu.linux@gmail.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).