mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Karim Yaghmour <karim@opersys.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Adeos nanokernel for Linux kernel
Date: Tue, 4 Jun 2002 16:10:02 +0000	[thread overview]
Message-ID: <20020604161001.K36@toy.ucw.cz> (raw)
In-Reply-To: <3CFB2A38.60242CBA@opersys.com>

Hi!

> We have released the initial implementation of the Adeos nanokernel.
> The following is a complete description of its background, its
> implementation, its API, and its potential uses. Please also see the
> press release (http://www.freesoftware.fsf.org/adeos/pr-2002-06-03.en.txt)
> and the project's workspace (http://freesoftware.fsf.org/projects/adeos/).
> The Adeos code is distributed under the GNU GPL.

Sounds interesting...

> Here are some of the possible uses for Adeos (this list is far
> from complete):
> 1) Much like User-Mode Linux, it should now be possible to have 2
> Linux kernels living side-by-side on the same hardware. In contrast
> to UML, this would not be 2 kernels one ontop of the other, but
> really side-by-side. Since Linux can be told at boot time to use
> only one portion of the available RAM, on a 128MB machine this
> would mean that the first could be made to use the 0-64MB space and
> the second would use the 64-128MB space. We realize that many
> modifications are required. Among other things, one of the 2 kernels
> will not need to conduct hardware initialization. Nevertheless, this
> possibility should be studied closer.

Also, unlike UML, kernels are not protected from each other.

> 2) It follows from #1 that adding other kernels beside Linux should
> be feasible. BSD is a prime candidate, but it would also be nice to
> see what virtualizers such as VMWare and Plex86 could do with Adeos.
> Proprietary operating systems could potentially also be accomodated.

So if your FreeBSD+Linux combination crashes, you do not know if Linux or 
FreeBSD caused it.

> 5) Drivers who require absolute priority and dislike other kernel
> portions who use cli/sti can now create a domain of their own
> and place themselves before Linux in the ipipe. This provides a
> mechanism for the implementation of systems that can provide guaranteed
> realtime response.

This is same approach rtLinux takes, right?
								Pavel
-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


  parent reply	other threads:[~2002-06-04 19:52 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-03  8:35 Karim Yaghmour
2002-06-03  8:46 ` Erik Andersen
2002-06-03  8:56   ` Alessandro Rubini
2002-06-03  9:14   ` Karim Yaghmour
2002-06-03  9:52     ` Erik Andersen
2002-06-03 10:05       ` Alessandro Rubini
2002-06-03 10:12       ` Karim Yaghmour
2002-06-03 10:33         ` Erik Andersen
2002-06-03 10:38           ` Karim Yaghmour
2002-06-03 11:05         ` Daniel Phillips
2002-06-03  9:26 ` Daniel Phillips
2002-06-04 19:29   ` Oliver Xymoron
2002-06-05  2:20     ` Daniel Phillips
2002-06-05  2:40       ` Oliver Xymoron
2002-06-05  2:57         ` Daniel Phillips
2002-06-05 13:51           ` Oliver Xymoron
2002-06-05 14:25             ` Daniel Phillips
2002-06-05 15:37               ` Oliver Xymoron
2002-06-05 17:32                 ` Daniel Phillips
2002-06-05 18:06                   ` Mark Mielke
2002-06-05 18:26                     ` Daniel Phillips
2002-06-05 19:13                       ` Oliver Xymoron
2002-06-05 19:40                         ` Daniel Phillips
2002-06-05 20:51                           ` Mark Mielke
2002-06-05 21:45                             ` Daniel Phillips
2002-06-05 21:22                           ` Oliver Xymoron
2002-06-05 21:55                             ` Daniel Phillips
2002-06-06  8:52                               ` Peter Wächtler
2002-06-06 10:58                                 ` Daniel Phillips
2002-06-06 14:03                                   ` Peter Wächtler
2002-06-06 16:53                                     ` Daniel Phillips
2002-06-05 20:48                         ` Mark Mielke
2002-06-06  8:34                           ` Peter Wächtler
2002-06-08 13:50             ` john slee
2002-06-08 13:59               ` Thunder from the hill
2002-06-06 21:21           ` Pavel Machek
2002-06-07  1:35             ` Mark Mielke
2002-06-07  2:42               ` Daniel Phillips
2002-06-07  2:48                 ` Mark Mielke
2002-06-07 10:32                   ` Daniel Phillips
2002-06-07 21:35                     ` Pavel Machek
2002-06-05  9:41         ` Ingo Oeser
2002-06-05 18:20           ` Karim Yaghmour
2002-06-05  3:56       ` J Sloan
2002-06-05  4:08         ` Daniel Phillips
2002-06-05  7:28           ` Eric W. Biederman
2002-06-05 11:15           ` Peter Wächtler
2002-06-05 12:56             ` Daniel Phillips
2002-06-05 11:11       ` Peter Wächtler
2002-06-05 16:55       ` Rob Landley
2002-06-04 16:10 ` Pavel Machek [this message]
2002-06-04 19:59   ` Karim Yaghmour
2002-06-04 21:53   ` Karim Yaghmour
2002-06-04 23:06     ` Alan Cox
2002-06-05  4:00   ` Daniel Phillips
2002-06-05  9:24 Martin.Knoblauch
2002-06-05 19:01 Paul Zimmerman
2002-06-05 19:11 ` Karim Yaghmour
2002-06-05 20:17 ` Daniel Phillips

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=20020604161001.K36@toy.ucw.cz \
    --to=pavel@suse.cz \
    --cc=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®