home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!cs.utexas.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!hamblin.math.byu.edu!yvax.byu.edu!cunyvm!psuvm!bgt101
- Newsgroups: comp.sys.amiga.misc
- Subject: Re: Why doesn't Amiga core-dump? *sigh*
- Message-ID: <92323.182614BGT101@psuvm.psu.edu>
- From: Blaise Tarr <BGT101@psuvm.psu.edu>
- Date: Wed, 18 Nov 1992 18:26:14 EST
- References: <BxL1K6.CnG@usenet.ucs.indiana.edu><1992Nov15.103719.9969@sth.frontec.se>
- <92323.003545BGT101@psuvm.psu.edu><1992Nov18.133139.21744@ifi.unizh.ch>
- Organization: Penn State University
- Lines: 24
-
- In article <1992Nov18.133139.21744@ifi.unizh.ch>,
- cschneid@avalon.physik.unizh.ch (Schneider Christian) says:
-
- >If it doesn't _seem_ to be difficult to you, the only reason is you didn't
- >understand the problems involved in Memory Protection.
- >AmigaOS was not, is not and never will be designed for MP. Take message
- >passing as an example...
-
- Never say never :-). On page 456 of the 2.0 RKRM under a description of
- the MEMF_PUBLIC flag it says: "... Although this flag doesn't do anything
- right now, using this flag will help ensure compatibility with possible
- future features of the OS (like virtual memory and memory protection)."
- ^^^^^^^^^^^^^^^^^
-
- Anyways, message passing isn't necessarily an impossible obstacle to overcome
- on the road to memory protection. When a message is passed (or rather a
- pointer to the message), the area with the message essentially belongs to
- the process receiving the message. The MMU tables can be modified so the
- receiving process has access to the message until it has sent a ReplyMsg().
-
- /// Blaise Tarr
- ///
- \\\/// BGT101@psuvm.psu.edu "Typically, the subject being copied
- \XX/ tarr@cs.psu.edu is terminated." -CSM 101
-