[okl4-developer] how are made syscall in OKLinux?

[Harry Vennik]

Op 26-jun-2008, om 9:59 heeft Antonin SUBTIL het volgende geschreven:

> Hello,
>
> I'm currently working on porting syscalls from my own OS to its  
> virtualized version. Yet I've got some problems with entering to  
> syscalls and exiting.
>
> I've found that OKLinux thread send one IPC to some "OKLinux  
> syscall handler thread" which handle the syscall and return the  
> result by ipc : is that correct ? I'm still looking into the code...
This is correct.

>
> More generally, is there any doc on "how to port your OS's syscalls  
> to OKL4" ? (and some "how to port your own legacy OS to OKL4" would  
> be nice too)
Basically you'd port your legacy OS kernel to become a user-mode  
application running on top of OKL4, which exposes one or more  
interfaces that are accessible with normal OKL4 IPC call/reply. To  
make it easy, you can use IDL4 to describe the interfaces and then  
generate the actual IPC code with magpie.

The syscalls of the legacy OS will become members of the exposed  
interface(s).


>
> Thanks
>
> -- 
> Antonin Subtil,
> 35 rue Donissan
> FR-33000 Bordeaux
> +33 (0)6.77.40.17.69
>
> Economisez du papier, limitez votre production de déchets :  
> n'imprimez ce message que si nécessaire (et... en recto-verso) !
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer