From 8da0171e5ca3492cdb34422184a1c96acd0b5165 Mon Sep 17 00:00:00 2001 From: Kimplul Date: Sat, 21 May 2022 21:02:17 +0300 Subject: 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. --- TODO.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'TODO.txt') diff --git a/TODO.txt b/TODO.txt index 20f86a3..6c98139 100644 --- a/TODO.txt +++ b/TODO.txt @@ -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 -- cgit v1.3