| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2022-11-09 | update docs | Kimplul | |
| 2022-11-09 | add basic IPI structure | Kimplul | |
| 2022-10-21 | beautification | Kimplul | |
| 2022-10-21 | initial implementation of swap | Kimplul | |
| + Slightly unsure if it should be a syscall, or if assign would be enough. Also, which thread should run in a fork/spawn? For now, old thread, though this might increase latency. Or add swap flag to these calls? | |||
| 2022-10-21 | initial spawn implementation | Kimplul | |
| 2022-06-12 | add license texts | Kimplul | |
| 2022-06-11 | continue documentation | Kimplul | |
| 2022-06-09 | continue documentation | Kimplul | |
| 2022-05-28 | start implementing new proc/rpc handling | Kimplul | |
| + Essentially, separate root process and remote procedure call handling. I really should write down some documentation so I don't forget, but essentially: All threads share a common process virtual memory, and when a thread wants to make an rpc, it switches over to its own rpc vmem space that is linked to the remote process. | |||
| 2022-05-24 | make process loading more generic | Kimplul | |
 |
index : kmi | |
| ACTIVE - Kernel with migrating threads as IPC | kimi.h.kuparinen+kmi@gmail.com |
| aboutsummaryrefslogtreecommitdiff |