OOMTK Kernel

My idea is to make a very small and basic microkernel that will handle context switching, memory allocation and message passing. Everything else should be in separate servers. To make things worse, no application will be able to access the hardware directly. Instead, it will have to go through HAL (hardware abstraction layer) interface to get to hardware. The HAL will implement some basic methods, such as port i/o. The HAL will have to be ring0, but it will be a separate process from the kernel itself, so that it cannot generate an error that would block the kernel. There will also exist a process that will be responsible of reloading the servers if they crash (and if they registered to be reloadable).
Currently, it is very far from usable. Here's the current screenshot (just a bootable kernel with paging and descriptors set up):
No comments:
Post a Comment