🚀 go-pugleaf

Deven Corzine <deven@rpi.edu> writes in
Message-ID: <DEVEN.89May24025106@daniel.rpi.edu>

> Fine.  But the RKM's say interrupt code and data MUST be in
> MEMF_PUBLIC memory.  Why?

Interrupt code might be called up by any task in the system. Thus the Exec and
the MMU will think that the code executed is part of the calling task. If that
code and its data can are not accessible through the MMU by what the Exec
thinks is the current task, you get a priviledge violation error.

> And yes, virtual memory will have far less damaging effects
> than memory protection, with the design of the operating system -- the
> message passing mechanism, in particular.

I believe I already demonstrated why the contrary is true.

Valentin
_________________________________________________________________________
"An  operating  system  without         Name:   Valentin Pepelea
 virtual memory is an operating         Phonet: (613) 231-7476 (New!)
 system without virtue."                Bitnet: 451061@Uottawa.bitnet
                                        Usenet: Use cunyvm.cuny.edu gate
         - Ancient Inca Proverb         Planet: 451061@acadvm1.UOttawa.CA