From: Markus Franke <Markus.Franke@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Scheduling of different domains in Adeos
Date: Tue, 27 Feb 2007 08:52:03 +0100 [thread overview]
Message-ID: <45E3E323.7060209@domain.hid> (raw)
In-Reply-To: <45E3116E.70402@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
Jan Kiszka wrote:
> See above: each domain (which may contain an OS) has a certain priority,
> and the one with the highest priority which has events pending gets the
> CPU. That's what the Adeos/I-pipe patch does on event arrival or domain
> suspension.
Ok, this I know already.
> Adeos doesn't do full CPU virtualisation. Therefore, the domains must
> cooperate on those resources (memory management, FPU, etc.) that aren't
> switched by the nano-kernel. Adeos is not qemu or kvm, if this is what
> you have in mind.
So if you want to get working more than one operating system, each
embodied in it's own domain, you have to adapt the operating systems in
order to get also some kind of CPU virtualization. But these changes are
not part of the Adeos-Patches for the Linux kernel, right?
Has anybody ever tried to set up a system with let's say two Linux
kernels working on top of Adeos, simultaneously?
Regards,
Markus
[-- Attachment #2: Markus.Franke.vcf --]
[-- Type: text/x-vcard, Size: 245 bytes --]
begin:vcard
fn:Markus Franke
n:Franke;Markus
adr;quoted-printable:;;Vettersstra=C3=9Fe 64/722;Chemnitz;Saxony;09126;Germany
email;internet:Markus.Franke@domain.hid
x-mozilla-html:FALSE
url:http://www.tu-chemnitz.de/~franm
version:2.1
end:vcard
next prev parent reply other threads:[~2007-02-27 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 9:49 [Adeos-main] Scheduling of different domains in Adeos Markus Franke
2007-02-25 10:15 ` Jan Kiszka
2007-02-26 15:20 ` Markus Franke
2007-02-26 16:57 ` Jan Kiszka
2007-02-27 7:52 ` Markus Franke [this message]
2007-02-27 10:13 ` Jan Kiszka
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=45E3E323.7060209@domain.hid \
--to=markus.franke@domain.hid \
--cc=adeos-main@gna.org \
--cc=jan.kiszka@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.