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 12:22:37 -0400 [thread overview]
Message-ID: <3D12014D.55739F1A@opersys.com> (raw)
In-Reply-To: 20020620121703.GA2544@domain.hid
Jacob Gorm Hansen wrote:
> We are currently trying to make L4Linux (linux2.2 running on the L4
> micro kernel) boot several in L4Linux instances.
>
> The good thing about L4 is that it gives us address space protection and
> IPC, but sometimes the 'every linux tasks is an l4 task' way of doing
> things seems a bit much.
>
> We want to be able to migrate entire OSes between machines, and thus we
> cannot trust the OSes to be friendly or correct.
>
> If we had the time, it seems that implementing protection in adeos would
> be interesting and easier to work with than L4 (which is a very nice
> u-kernel btw).
L4 is very interesting indeed. Last I read about it, though, its
licensing was problematic (i.e. couldn't be released "open source"
because of the funding of the project) and it is very hardware dependent
(in order to achieve better performance). Is this still true?
I understand the need to be able to migrate entire OSes between
machines. Because we do not virtualize the physical RAM, this
may a little harder to do with Adeos. But since we assume that
we can modify the OSes to better interact with Adeos, then it
should not be that much harder to implement code that "rewires"
the kernels' mappings. Of course, this would require some work,
and time ... ;)
Cheers,
Karim
===================================================
Karim Yaghmour
karim@domain.hid
Embedded and Real-Time Linux Expert
===================================================
next prev parent reply other threads:[~2002-06-20 16:22 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
2002-06-20 12:17 ` Jacob Gorm Hansen
2002-06-20 16:22 ` Karim Yaghmour [this message]
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=3D12014D.55739F1A@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.