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
begin:vcard fn:Markus Franke n:Franke;Markus adr;quoted-printable:;;Vettersstra=C3=9Fe 64/722;Chemnitz;Saxony;09126;Germany email;internet:[EMAIL PROTECTED] x-mozilla-html:FALSE url:http://www.tu-chemnitz.de/~franm version:2.1 end:vcard
_______________________________________________ Adeos-main mailing list [email protected] https://mail.gna.org/listinfo/adeos-main
