microkernel
Here are 90 public repositories matching this topic...
https://github.com/seL4/seL4/blob/master/manual/parts/cspace.tex#L430 gives a good example to explain CSpace addressing. It is clear enough to introduce the addressing concept, but with coding practice it's better to make them more precise.
When passing address arguments in multi-level CNodes, the index field, i.e. its address, must right aligned the significant bits according its depth. In a
-
Updated
Feb 5, 2020 - Rust
-
Updated
Jun 2, 2020 - C++
-
Updated
Jun 5, 2020 - C
See thor's system/legacy-pc
-
Updated
Dec 2, 2019 - Rust
-
Updated
Jun 7, 2020 - C
-
Updated
May 31, 2020 - C++
-
Updated
Nov 11, 2019 - C
-
Updated
Mar 1, 2020 - Rust
-
Updated
Jun 2, 2020 - Ada
-
Updated
Dec 21, 2017 - PHP
-
Updated
Nov 27, 2019 - C
-
Updated
Jun 4, 2020 - C++
-
Updated
May 27, 2020 - C
Document all modules
-
Updated
Mar 31, 2017 - C
-
Updated
Jun 4, 2020 - C++
-
Updated
Jun 7, 2020 - C
-
Updated
Nov 30, 2019 - C
-
Updated
Feb 23, 2020 - C++
Improve this page
Add a description, image, and links to the microkernel topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the microkernel topic, visit your repo's landing page and select "manage topics."


For every scheme a fully running kernel has, the following functions need to be documented, if implemented. In addition, the Scheme and SchemeMut traits should be documented with usage and the default operation.
Documentation should include usage, what access restrictions there are, what paths and dup arguments are valid, and what errors may be returned.
Path Operations