From: Jan Kiszka <jan.kiszka@domain.hid>
To: Markus.Franke@domain.hid
Cc: adeos-main@gna.org
Subject: Re: [Adeos-main] Scheduling of different domains in Adeos
Date: Mon, 26 Feb 2007 17:57:18 +0100 [thread overview]
Message-ID: <45E3116E.70402@domain.hid> (raw)
In-Reply-To: <45E2FAB3.2000305@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
Markus Franke wrote:
> Jan Kiszka wrote:
>> Scheduling takes place only based on the domain priority, each time a
>> new asynchronous event (interrupt) arrives or a domain reports to be
>> idle. There is no explicit source file or function called "scheduler",
>> you will find its logic in the dispatching code of pipelined interrupts
>> and in ipipe_suspend_domain().
>
> As far as I understood, it is possible to run more than operating system
> on top of Adeos, at a time. Adeos is said to be a resource
> virtualization layer and the CPU is also a resource, which has to be
> shared. But if there are more than one operating system, who decides
> which one get's the CPU?
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.
> The question is out of scope of the interrupt virtualization. It's just
> a question about CPU virtualization.
>
> Please correct me if I missunderstood something totally. :-)
>
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.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-02-26 16:57 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 [this message]
2007-02-27 7:52 ` Markus Franke
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=45E3116E.70402@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=Markus.Franke@domain.hid \
--cc=adeos-main@gna.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 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.