From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ronald G Minnich <rminnich@lanl.gov>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] moving 9load to 0x800000
In-Reply-To: <20020125163748.89D1019A6B@mail.cse.psu.edu>
Message-ID: <Pine.LNX.4.33.0201251008520.26941-100000@snaresland.acl.lanl.gov>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Date: Fri, 25 Jan 2002 10:12:20 -0700
Topicbox-Message-UUID: 45d6956c-eaca-11e9-9e20-41e7f4b1d025

On Fri, 25 Jan 2002 jmk@plan9.bell-labs.com wrote:

> You probably need to change at where load.c/ialloc() starts allocating
> (currently 3MB).

actually that ought to be ok with us.

Here's the problem. We're loading 9load from linuxbios. There is
significant usage of the area 0x10000 and up by linuxbios, so 9load has to
live elsewhere. 0x100000 won't do, since that's where the kernel goes.

So I hoped we could put the 9load code at 0x800000. I don't see a problem
with allocating at 3 MB, that leaves plenty of room for the kernel at 1
MB.

It ends up like this:

0-0x90000 linuxbios
0x100000-0x2fffff -- plan 9 kernel (when loaded)
0x300000          -- 9load allocator
0x800000          -- 9load code

Does that sound reasonable? Will the -T switch to ld fix all that needs
fixing or are there manifest constants somewhere we have to fix up too?

thanks

ron