All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@domain.hid>
To: Jacob Gorm Hansen <jg@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Address spaces in adeos
Date: Thu, 20 Jun 2002 00:21:56 +0000	[thread overview]
Message-ID: <3D112024.E4B7C59D@opersys.com> (raw)
In-Reply-To: 20020619130256.GA1529@domain.hid

Hello Jacob,

Jacob Gorm Hansen wrote:
> do you guys have any plans to implement protected address spaces, and means of
> communicating between them (like ipc)? There are some scenarios in which
> operating systems cannot be trusted not to sabotage eachother.

This is one of the scenarios which was discussed in the original
announcement. It is foreseeable, for instance, to have 2 OSes running
in the same RAM, each within its own physical boundaries:
Kernel A: 0-64MB
Kerbel B: 64-128MB

As with other nanokernels, the main mechanism to communicate between
such kernels would be soft interrupts. We could even foresee another
scenario where there's one part of the RAM that is reserved for
setting up shared memory regions between OSes.

There are 2 main "problems" in all these such scenarios:
1- There is no protection for physical accesses since all OSes have
can directly play with the hardware.
2- Page faults must be sent to the faulty domain only.

#2 is not really that hard to solve. We need to implement a page fault
demux which sends the page fault to the current domain only.

There is, unfortunately, no real way to get around #1 without adding
extra virtualization layers. Since we are assuming stable kernels
with "intelligent" code, however, then it should not be a problem.

Karim

===================================================
                 Karim Yaghmour
               karim@domain.hid
      Embedded and Real-Time Linux Expert
===================================================


  reply	other threads:[~2002-06-20  0:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020617120652.36799.qmail@domain.hid>
2002-06-17 12:42 ` [Adeos-main] Re: My first tests with adeos!!! Karim Yaghmour
2002-06-18  7:17   ` mohan kumar
2002-06-18 10:29     ` Karim Yaghmour
2002-06-18 10:34       ` Karim Yaghmour
2002-06-19  5:17       ` mohan kumar
2002-06-19 12:24         ` Philippe Gerum
2002-06-19 13:02           ` [Adeos-main] Address spaces in adeos Jacob Gorm Hansen
2002-06-20  0:21             ` Karim Yaghmour [this message]
2002-06-20 12:17               ` Jacob Gorm Hansen
2002-06-20 16:22                 ` Karim Yaghmour
2002-06-21  8:00                   ` Jacob Gorm Hansen
2002-06-19 21:32         ` [Adeos-main] Re: My first tests with adeos!!! Philippe Gerum
2002-06-18  7:29   ` [Adeos-main] Re: [rtai] " Guennadi Liakhovetski
2002-06-18  8:27     ` Wolfgang Denk
2002-06-18  7:39   ` [Adeos-main] " mohan kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D112024.E4B7C59D@opersys.com \
    --to=karim@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=jg@domain.hid \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.