To view parent comment, click here.
To read all comments associated with this story, please click here.
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.
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?





Member since:
2011-10-17
Norman,
Since Fiasco.OC has been forked, do you think it would be worthwhile to implement the change suggested here: http://os.inf.tu-dresden.de/pipermail/l4-hackers/2012/005361.html ?
That is getting rid of Sigma0 as done by other L4 or L4-like kernels... Or do you think diverging too much from the upstream kernel is not justifiable right now?