diff options
| author | Kimplul <kimi.h.kuparinen@gmail.com> | 2022-05-21 21:02:17 +0300 |
|---|---|---|
| committer | Kimplul <kimi.h.kuparinen@gmail.com> | 2022-05-21 21:02:17 +0300 |
| commit | 8da0171e5ca3492cdb34422184a1c96acd0b5165 (patch) | |
| tree | c125b7286f929c8ff7f8a2b938cec84328e99de4 /TODO.txt | |
| parent | 836026dbba64793afc0d2591ffdb6fb39b696977 (diff) | |
| download | kmi-8da0171e5ca3492cdb34422184a1c96acd0b5165.tar.gz kmi-8da0171e5ca3492cdb34422184a1c96acd0b5165.zip | |
add status info to memory mappings
+ next up would probably be to start working on process/thread
relationships, largely as documented. Still not entirely sure about
how I want to handle fork, but I suppose I might figure it out at some
point.
Diffstat (limited to 'TODO.txt')
| -rw-r--r-- | TODO.txt | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -2,7 +2,7 @@ + Implement more type operators in dbg, mainly intmax/uintmax and size_t -+ Add in mapping the same memory to two different processes ++ Add in mapping the same memory to two different processes (sort of?) + Create sensible thread handling + Add in init process loading + Make sure vmap is in 4K increments or whatever (fuck it, sure) @@ -14,7 +14,7 @@ details dumbass + Primarily memory should be allocated to a process through mmap-like functionality, but brk/sbrk can probably still be emulated. If s/brk maps memory that's later attempted to mmap, it fails, and vice versa. Apparently should be -acceptable by Unix standards. +acceptable by Unix standards. (or just make brk in libc a noop?) + Alignment can maybe still be used, though more in the sense of using larger pages? YES, CHECK common/vmem.c:map_fill_region! Should be implemented there as well |