Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ptsfa!hoptoad!academ!uhnix1!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: MMU operations (was Re: resource tracking problem)
Message-ID: <784@sugar.UUCP>
Date: Mon, 21-Sep-87 08:22:24 EDT
Article-I.D.: sugar.784
Posted: Mon Sep 21 08:22:24 1987
Date-Received: Thu, 24-Sep-87 05:20:44 EDT
References: <5118@jade.BERKELEY.EDU>
Organization: Sugar Land UNIX - Houston, TX
Lines: 15

> [what do we do to get the O/S to work in a protected memory environment]

There's already a hook for that. It's called MEMF_PUBLIC. If you specify
MEMF_PUBLIC in a call, you'll get memory in the common pool. If you don't,
you'll get memory attached to your local shuffle-able address space. Probably
MEMF_CHIP would get locked on the grounds that the hardware needs to get at it,
which might make it hard to make it private (due to granularity of the MMU).
Ideally, each task would see their PRIVATE memory always growing from the end of
CHIP, with PUBLIC memory mapped in up somewhere near the I/O page (or down in
CHIP if that's what it is). Alternatively, PRIVATE memory could be mapped to
start at the end of 68000 memory (if it's a 68020 version, right... 68000s
would still have to stay under 16 meg).
-- 
-- Peter da Silva `-_-' ...!hoptoad!academ!uhnix1!sugar!peter
--                 'U`  Have you hugged your wolf today?