Dear
We are currently working on the ukernel design and survey the L4 API interface. For Fiasco, it is implemented on L4/V2 and L4/X.0 interfaces.
If we implement a new u-kernel by ourselves that follows the same L4 API interface, will it still support the L4Env and L4Linux which will be put above this u-kernel? I think this issue is reasonable.
Thanks a lot!
Best Regards, Sean
On Fri Aug 29, 2008 at 14:07:50 +0800, Sean wrote:
We are currently working on the ukernel design and survey the L4 API interface. For Fiasco, it is implemented on L4/V2 and L4/X.0 interfaces.
If we implement a new u-kernel by ourselves that follows the same L4 API interface, will it still support the L4Env and L4Linux which will be put above this u-kernel? I think this issue is reasonable.
Of course, if it's the same interface, the software should run on it (otherwise it would not be close enough obviously).
Adam
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Sean schrieb:
Dear
We are currently working on the ukernel design and survey the L4 API interface. For Fiasco, it is implemented on L4/V2 and L4/X.0 interfaces.
That's only partially true for the latest Fiasco SVN version. We consider it implementing the L4.Fiasco spec, implementing L4v2 and several additions that have been inherited from other specs such as x0 or have been incorporated by ourselves.
If we implement a new u-kernel by ourselves that follows the same L4 API interface, will it still support the L4Env and L4Linux which will be put above this u-kernel? I think this issue is reasonable.
Since it is an ABI, not an API, when you implement a kernel providing the same ABI provided by Fiasco, you will be able to run L4Env and L4Linux on top, yes.
Bjoern - -- Dipl.-Inf. Bjoern Doebel Mail: doebel@tudos.org TU Dresden, OS Chair Phone: +49 351 463 38 799 Noethnitzer Str. 46 Fax: +49 351 463 38 284 01187 Dresden, Germany WWW: http://www.tudos.org
Dear
Thanks for the replies. In TUDOS wiki, it said that "In 2007 the actually supported API of Fiasco was too disjunct with the Version 2 API, so Fiasco received its own API name which is *L4.Fiasco*."
After browsing the fiasco website, I couldn't find the relative document about L4.Fiasco. Does L4.Fiasco kernel API and ABI release any reference documents?
Thanks again.
Best Regards, Sean
On Sat, Aug 30, 2008 at 5:40 PM, Björn Döbel doebel@os.inf.tu-dresden.dewrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Sean schrieb:
Dear
We are currently working on the ukernel design and survey the L4 API interface. For Fiasco, it is implemented on L4/V2 and L4/X.0 interfaces.
That's only partially true for the latest Fiasco SVN version. We consider it implementing the L4.Fiasco spec, implementing L4v2 and several additions that have been inherited from other specs such as x0 or have been incorporated by ourselves.
If we implement a new u-kernel by ourselves that follows the same L4 API interface, will it still support the L4Env and L4Linux which will be put above this u-kernel? I think this issue is reasonable.
Since it is an ABI, not an API, when you implement a kernel providing the same ABI provided by Fiasco, you will be able to run L4Env and L4Linux on top, yes.
Bjoern
Dipl.-Inf. Bjoern Doebel Mail: doebel@tudos.org TU Dresden, OS Chair Phone: +49 351 463 38 799 Noethnitzer Str. 46 Fax: +49 351 463 38 284 01187 Dresden, Germany WWW: http://www.tudos.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIuRV6P5ijxgQLUNkRAhJvAJ0WUlEDwAbdvmV6HP40EF2OIfTIdACffs7v LiOFYAGCTzW7BoMmZI0Lz3k= =wSa+ -----END PGP SIGNATURE-----
On Mon Sep 01, 2008 at 16:58:21 +0800, Sean wrote:
In TUDOS wiki, it said that "In 2007 the actually supported API of Fiasco was too disjunct with the Version 2 API, so Fiasco received its own API name which is *L4.Fiasco*."
After browsing the fiasco website, I couldn't find the relative document about L4.Fiasco. Does L4.Fiasco kernel API and ABI release any reference documents?
There is no specification of the additions available, however the userland bindings use those. So the l4sys package somwhat describes what's available.
Adam
l4-hackers@os.inf.tu-dresden.de