home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!Sirius.dfn.de!mailgzrz.TU-Berlin.DE!math.fu-berlin.de!uni-paderborn.de!aurel
- From: aurel@uni-paderborn.de (Aurel Balmosan)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: physical memory protection with MMU
- Date: 17 Nov 1992 09:43:08 GMT
- Organization: Uni-GH Paderborn, Germany
- Lines: 28
- Distribution: worlD
- Message-ID: <1eaercINN3ij@uni-paderborn.de>
- References: <nn.geht.nicht.die-zweite.121192@uni-paderborn.de> <1duvk4INN65q@darkstar.UCSC.EDU> <Bxo6pD.LnG@unix.portal.com> <1e26guINN9gl@darkstar.UCSC.EDU>
- NNTP-Posting-Host: miro.uni-paderborn.de
- Keywords: mmu, memory, task
-
- I think I found a way to handle memory protection which would work with
- all existing programs.
- On condition that the MMU can handle any number of memory segments,
- the system should distinguish between public memory (MEMF_PUBLIC) and
- none public memory (allocated without MEMF_PUBLIC). If some task would
- access a public memory segment of an other there would be no
- MMU-interception. If a task try to access none public memory (not equal with
- non allocated memory!) a execption would be the result.
-
- In practice, in the <task-switch> the task should insert his private memory
- segments and in the <task-launch> the task should remove his private memory
- segments.
-
- Note: Each task has its normal address space.
- The MMU is used only for generating execptions.
- The MMU must handle any number of memory segments.
- In advaced use an allocated memory segment could have public and
- private (eg. libraries have public data and private data)
-
-
- PS: You don't need a MMU. You only need an execption generator(eg. BUS-Error).
- And this would be (easy) to build.
-
- Could this a way to a real secure amiga ???
-
- --
- Alexandru-Aurel Balmosan aurel@uni-paderborn.de
- University of Paderborn (Germany)
-