1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
|
# kogata operating system project
kogata operating system : small and <del>beautiful</del>small.
## Project characteristics
### Written in C
I have considered using higher-level languages but for lack of understanding of
the associated compiler, I never have had the same impression of understanding
exactly what was happening that I had with C. Also, the necessity of a runtime
is bothering. I do regret not being able to exploit the magic of strongly typed
functionnal languages, but what can I do...
### Monolithic design
I would have liked to do a microkernel, but the necessity for asynchronous
communication makes it much more difficult to code, and contradicts the goal of
having simple and straightforward code.
### Emphasis on code quality and reliability
The code for the project must make sense, be simple and straightforward, and be
easily understandable in complete detail so that we can track bugs and extend
the system more easily.
### Goal : small and cool
I would love to have kogata fit on a 1.44MB floppy and run with a full GUI and
some cool apps (remember the QNX demo floppy!). Also, I want to be able to use
it on older computers and prove that such machines can still be put to use.
## How to build
### Requirements
* git for accessing the repository
* `i586-elf` cross-compiler built by [these scripts](http://adnab.me/cgit/cross-scripts.git/about/).
* nasm
* for testing, either qemu or bochs
### Building and running
To build, clone the repo somewhere and simply run:
$ make
Launching qemu is also included in the makefile:
$ make run_qemu
Warning: dependencies between portions of code are not necessarily well handled
by the makefile system. If you made changes and the OS fails miserably, try
doing a `make rebuild` before blaming your code.
### Runing the tests
The directory `src/tests/` contains a few tests for some of the core
components. The running of these tests is automated. To run the test suite,
simply invoke the corresponding make target (everything is rebuilt before
running the tests):
$ make run_tests
## Structure of the project
### Modules
* The kernel
* Libraries
* `libkogata` : basic system functionnality (memory allocator, mutexes, debugging)
* `libc` : implementation of a (very restricted) subset of the standard C library, basically just
the functions that were needed somewhere
* `libalgo` : usefull data structures (hashtables, AVL trees, maybee more in the future)
* Userspace : not much work done yet
### Files in the repository
doc/ documentation (none yet, sorry!)
src/
src/kernel/ code for the kogata kernel
src/common/ code shared between kernel and userspace libs
src/lib/ code for userspace libraries
src/apps/ userspace binaries
src/tests/ test suite
## Roadmap
### Plans for soon
* Implement missing syscalls
* Write device drivers : VGA, keyboard, ATA, FAT, VESA
### Things to design
* Cache architecture :
- A RAM file is basically a bunch of pages that contain the data (rather than a segment of
malloc()'ed memory)
- A framebuffer device is basically a bunch of pages at a fixed hardware location, that cannot
grow
- In the two previous cases, the pages are never freed : they are not a cache, they are the
data itself.
- In the case of an on-disk file, the pages are a copy of the file's data that is originally
on-disk, and we might want to free these pages even while a process is using them, because
we can always reload them from the disk.
- An on-disk file with a page cache must be aware of all the places where the page is mapped,
so that it can unmap it when reclaiming pages.
- Simpler model : cached pages cannot be freed while the file is open with `FM_MMAP`
* Reclaiming physical memory :
- Freeing some cached stuff, ie swapping pages from mmap regions
- Swapping pages from processes non-mmap regions (ie real data regions)
* IPC
* How does a process exit, what does it do, how do processes synchronize ?
* Have several threads in a single process
* Better handling of errors (rather than panicing) ; userspace apps should not
have the possibility of crashing the system
* How does a process transmit information (such as environment, arguments, file
descriptors) to its children ?
### Things not sure
* VFS thread safety : is the design correct ? (probably)
### Plans for the later future
* Module system for extending the kernel
* In userspace, simple Scheme-like scripting language
* The obvious stuff ;-)
## Licence
None of the source files have a licence header because it's cumbersome. All the
code and associated documentation found in this repository is released under
the ISC licence as detailed in the `COPYING` file.
|
