From: Karim Yaghmour <karim@domain.hid>
To: Jacob Gorm Hansen <jg@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Re: RTOS over Adeos document
Date: Mon, 04 Nov 2002 13:39:31 -0500 [thread overview]
Message-ID: <3DC6BEE3.3AD48CCE@opersys.com> (raw)
In-Reply-To: 20021104172711.GA2989@domain.hid
Jacob Gorm Hansen wrote:
> If Adeos gets spaces like Space, then it would be interesting.
> Otherwise I don't think it is possible, because we need to protect guest
> OSes against eachother.
You don't need to do that if each OS is stable and doesn't behave
randomly, which we assume is a fine description of Linux. As long
as the PCI probe is modified to only reveal the devices the OS
instance is supposed to see, then all other hardware should be
out of reach.
BTW, I've went through the L4Linux source code briefly and it was
interesting to see how they take care of cli/sti. They too redefine
those functions :) However, they use L4's IPC mechanisms to
implement cli/sti, which is kind of interesting.
Karim
===================================================
Karim Yaghmour
karim@domain.hid
Embedded and Real-Time Linux Expert
===================================================
next prev parent reply other threads:[~2002-11-04 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 8:26 [Adeos-main] RTOS over Adeos document Girish Wadhwani
2002-10-29 9:44 ` [Adeos-main] " Philippe Gerum
2002-11-04 10:07 ` Girish Wadhwani
2002-11-04 15:20 ` Karim Yaghmour
2002-11-04 15:41 ` Jacob Gorm Hansen
2002-11-04 17:05 ` Karim Yaghmour
2002-11-04 17:27 ` Jacob Gorm Hansen
2002-11-04 18:39 ` Karim Yaghmour [this message]
2002-11-06 10:45 ` Jacob Gorm Hansen
2002-11-05 9:08 ` Girish Wadhwani
2002-11-05 10:21 ` Jacob Gorm Hansen
2002-11-05 23:24 ` Girish Wadhwani
2002-11-05 23:55 ` Karim Yaghmour
2002-11-04 17:27 ` Philippe Gerum
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=3DC6BEE3.3AD48CCE@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.