Markus Franke wrote: > 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?
They are included as far as Linux as root domain is concerned, i.e. the lowest prioritised domain, hosting the whole stack. > > Has anybody ever tried to set up a system with let's say two Linux > kernels working on top of Adeos, simultaneously? Don't know, but I also don't think so. There is still quite a difference between stacking Linux and Xenomai on top of Adeos (with Linux as root). Xenomai was built with the constraints of running cooperatively on top of Linux already in mind. Jan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Adeos-main mailing list [email protected] https://mail.gna.org/listinfo/adeos-main
