home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!mcsun!sunic!aun.uninett.no!news.uit.no!borgen
- From: borgen@stud.cs.uit.no (Boerge Noest)
- Subject: Re: physical memory protection with MMU
- References: <1992Oct26.162400@uni-paderborn.de> <heinz.04a3@edohwg.adsp.sub.org>
- Sender: news@news.uit.no (USENET News System)
- Organization: University of Tromsoe, Norway
- Date: Tue, 10 Nov 1992 20:12:24 GMT
- Message-ID: <1992Nov10.201224.17361@news.uit.no>
- Lines: 25
-
- In article <heinz.04a3@edohwg.adsp.sub.org> heinz@edohwg.adsp.sub.org (Heinz Wrobel) writes:
- >But how?
-
- Give me a memory.library:
- token protect( startaddress, endaddress);
- bool unprotect( mytoken);
- tokenized_AllocMem( size);
- tokenized_FreeMem( address);
-
- Perhaps it needs some exec hacking(when task switching?).
- Should only permit protecting your own hunks, and only
- tokenized_AllocMem'ed memory?
-
- My point is; give me the chance to protect what _I_ know should be
- protected, and let me do this after my program has started.
-
- Later we can yell at C= to give us some new hunks.
-
- >Heinz Wrobel, Edotronik GmbH (ECG018)
-
- Waddayathink?
- --
- |/// borgen@stud.cs.uit.no (Boerge Noest) | Amiga B2000 \\\|
- |// Box 218, 9001 Tromsoe, Norway | Remember to :-) when needed \\|
- |/ The worlds northernmost university | Life is worth living. \|
-