Welcome, Guest. Please login or register.

Author Topic: Memory Protection AGAIN  (Read 8364 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline shoggoth

  • Full Member
  • ***
  • Join Date: Dec 2004
  • Posts: 223
    • Show all replies
Re: Memory Protection Again
« on: April 01, 2008, 02:27:44 PM »
Quote

bloodline wrote:
Quote

shoggoth wrote:
Couldn't this approach be used in AmigaOS as well?


It's easy to put Memory Protection into AmigaOS... but it will break all exisiting apps since they do not tell the OS that that want to share data...

What you seem to be sugesting is sandboxing the old apps... this is indeed the only way to add MP :-)


Maybe I'm completely lost, but let's say there is a default state for legacy applications, identical to what I referred to as "global" in my previous post. Any application that hasn't explicitly declared itself as being memory protection aware will run in this mode. An extra hunk in the binary format could declare the protection mode for each segment. The OS treats such binaries differently compared to legacy binaries. The result is protection for "modern" apps, while keeping compatibility (and risks) with older apps.

(note - I haven't exactly fooled around with kernel design, so take this as food for debate rather than proper argumentation)
 

Offline shoggoth

  • Full Member
  • ***
  • Join Date: Dec 2004
  • Posts: 223
    • Show all replies
Re: Memory Protection Again
« Reply #1 on: April 01, 2008, 03:56:58 PM »
Quote

bloodline wrote:
But this thread isn't about how to build a sandbox, it is about ideas to retrofit MP into AmigaOS and why it isn't really possible :-)


Ah, sorry, my bad. I thought it was about memory protection in an AmigaOS-like environment :)