Linked by nfeske on Thu 28th Feb 2013 12:08 UTC
OSNews, Generic OSes The just released version 13.02 of the Genode OS Framework comes with major improvements of the underlying kernels. Using the NOVA kernel, the framework can be used to build custom operating systems for IOMMU-enabled machines while also leveraging hardware virtualization. Using Genode's custom kernel or the Fiasco.OC kernel, the new version targets ARM Cortex-A15-based systems such as the Exynos 5250 SoC.
Thread beginning with comment 554002
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Very Impressive
by nfeske on Fri 1st Mar 2013 10:40 UTC in reply to "RE[2]: Very Impressive"
nfeske
Member since:
2009-05-27

I definitely support going this route. In my perception, sigma0 has no tangible purpose. So I see no point in having it included in the trusted computing base. In contrary, it caused us serious (priority inversion) problems in the past, and right now, we are struggling with caching issues on ARM, which may be partially attributed to sigma0 as well (because sigma0 makes it impossible to fully avoid inconsistencies of cache attributes). In this respect, removing it would be a relief.

Another benefit from getting rid of it (and 'bootstrap' when we are at it) would be to dissolve the dependencies of Genode from L4re packages such as l4util and uclibc. This way, both the 'make prepare' step and the build step would become much faster. Right now, we need to download and build uclibc just to be able to use the kernel, which is hard to justify.

Reply Parent Score: 2

RE[4]: Very Impressive
by jayrulez on Fri 1st Mar 2013 12:55 in reply to "RE[3]: Very Impressive"
jayrulez Member since:
2011-10-17

You are right. I definitely agree with this decision.

There are a few directories under l4/pkg that are checked out during the "make prepare" step. Which other ones are feasible to remove from the trusted computing base.

I figure you would keep l4sys, libvcpu, cxx, bootstrap, ldscripts and maybe the drivers-frst?

Reply Parent Score: 1

RE[5]: Very Impressive
by nfeske on Fri 1st Mar 2013 13:21 in reply to "RE[4]: Very Impressive"
nfeske Member since:
2009-05-27

I would strive to keep solely pkg/l4sys, which contains the header files that form the syscall bindings of the kernel.

Reply Parent Score: 2