From: Joel Soete <soete.joel@tiscali.be>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Jeff Dike <jdike@karaya.com>,
parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] B132L outperforms C160 - 64-bit userland needed?
Date: Sun, 21 Aug 2005 10:29:42 +0000 [thread overview]
Message-ID: <43085796.3080309@tiscali.be> (raw)
In-Reply-To: <20050820235516.GE2756@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
> On Sat, Aug 20, 2005 at 05:41:26PM -0600, Grant Grundler wrote:
>
>>On Sat, Aug 20, 2005 at 06:39:46PM +0000, Joel Soete wrote:
>>
>>>Any idea about the possibility to port um?
>>
>>um == User Mode Linux?
>>
>>It's possible. :^)
>>I'm not doing it. ;^)
>
>
> We gave Jeff Dike a 712 a few years ago ... hey Jeff, how's that going? ;-)
>
Ah cool ;^)
Jeff,
I don't have time to read all interesting <http://user-mode-linux.sourceforge.net/arch-port.html>
but my main problem is always:
[...]
Address space layout
Before delving into the code, you need to do some high-level conceptual thinking about how to organize the address space of a
UML process. UML maps its executable, physical memory, and kernel virtual memory into the address space of each of its processes.
You need to decide where to put each of these so as to minimize the likelihood of a process trying to allocate that memory for its
own use.
The only arch hook at this point is where in the address space the UML binary is going to load. The other addresses are still
hard-coded because they happen to work for both i386 and ppc. UML puts its own memory in the area starting at 0x5000000 and process
stacks 4M below its own process stack. These choices may not work on all architectures, so feel free to generalize them. To locate a
likely area on your arch, staring at /proc/<pid>/maps of various processes on the host has been the technique so far.
[...]
Any advise for the address space to use for hppa?
Thanks in advance,
Joel
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-08-21 10:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 8:27 [parisc-linux] B132L outperforms C160 - 64-bit userland needed? Joel Soete
2005-08-20 6:26 ` Grant Grundler
[not found] ` <430778F2.8020406@tiscali.be>
[not found] ` <20050820234126.GA20524@colo.lackof.org>
2005-08-21 9:42 ` Joel Soete
[not found] ` <20050820235516.GE2756@parcelfarce.linux.theplanet.co.uk>
2005-08-21 10:29 ` Joel Soete [this message]
2005-08-21 14:19 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2005-08-16 9:23 Kurt Fitzner
2005-08-16 13:00 ` Michael S. Zick
2005-08-17 0:03 ` Kurt Fitzner
2005-08-17 1:32 ` John David Anglin
2005-08-17 1:48 ` Michael S. Zick
2005-08-17 3:43 ` Kurt Fitzner
2005-08-17 6:37 ` Grant Grundler
2005-08-17 14:16 ` John David Anglin
2005-08-17 6:19 ` Grant Grundler
2005-08-17 18:42 ` Kurt Fitzner
2005-08-17 18:56 ` Kyle McMartin
2005-08-17 19:40 ` Andrew Sharp
2005-08-18 5:27 ` Kurt Fitzner
2005-08-18 7:17 ` Grant Grundler
2005-08-20 6:21 ` Grant Grundler
2005-08-17 20:38 ` Carlos O'Donell
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=43085796.3080309@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=jdike@karaya.com \
--cc=matthew@wil.cx \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.