kmi/src/regions.c, branch master ACTIVE - Kernel with migrating threads as IPC https://metanimi.dy.fi/cgit/kmi/atom?h=master 2024-11-02T14:34:38Z check spawn exhaustion 2024-11-02T14:34:38Z Kimplul kimi.h.kuparinen@gmail.com 2024-11-02T14:34:38Z urn:sha1:17fd9daf39cf79ae310c1b7d0eb459802517dc6a initial exec support 2024-11-02T13:28:23Z Kimplul kimi.h.kuparinen@gmail.com 2024-11-02T13:28:23Z urn:sha1:d127146846f4d6561e15000d1469b715dafdb627 improvements to shared memory handling 2024-08-30T16:20:21Z Kimplul kimi.h.kuparinen@gmail.com 2024-08-30T16:20:21Z urn:sha1:314bca3dc19a864c76153bfcd5a58be8c40000f9 + Now each shared region is reference counter (technically each region is refernce counted, private regions just have a count of 1). Also, syscalls that touch the TLB get flushed, but should probably look into where else this flushing might be needed. fix a couple memory issues 2024-08-30T15:54:12Z Kimplul kimi.h.kuparinen@gmail.com 2024-08-30T15:54:12Z urn:sha1:ec30538a81c0e900797f4d88c1ee059afa7d9617 + get_mem_node() clears out the memory so we don't accidentally read stale flags + Thread creation simplified a bit, each thread references itself and data freeing is based on when the reference count reaches zero. convert addr to page in find_closest_used_region 2024-08-27T16:10:55Z Kimplul kimi.h.kuparinen@gmail.com 2024-08-27T16:10:55Z urn:sha1:cb1fd73f6b76c2297772f6faccb9b46b99f55e2c fix memory leaks destroying threads 2024-08-26T20:00:55Z Kimplul kimi.h.kuparinen@gmail.com 2024-08-26T20:00:55Z urn:sha1:3f194f1c7264945a63b0018b159cc83bd9385c59 add malloc test 2024-08-21T20:31:48Z Kimplul kimi.h.kuparinen@gmail.com 2024-08-21T20:31:48Z urn:sha1:97ffab0a8472981b927d0f4e81bb72f6ecd69b86 small fixes to issues reported by analyzer 2024-08-17T21:17:35Z Kimplul kimi.h.kuparinen@gmail.com 2024-08-17T21:17:35Z urn:sha1:ab011165cd440b5535d39febd8118e3e26b64b57 + Currently analyzer has to be run manually with something like make CFLAGS='-fanalyzer -Wno-analyzer-infinite-loop' I use an infinite loop as an assert, I know it's not great/technically UB but it's just a fallback. + Analyzer is still somewhat limited, I could add in more attributes about different functions, such as memory allocation sizes etc. + If I ever set up a CI pipeline, remember to use analyzer? start working on tests 2024-07-09T19:12:27Z Kimplul kimi.h.kuparinen@gmail.com 2024-07-09T19:12:27Z urn:sha1:e8a1df103cc28419dd7d4439c0b1d1739d110f78 + Current setup will likely not last long, just a stopgap until I figure out how I want to build each testcase etc. Probably dir based, but I'll probably add some scripts that generate the build rules for each test case (or binary?). Also, should probably put ouput files in a build directory and keep the source clean, but again, good enough for now. Will have to start implementing more extensive tests, and probably come up with some way to compare textual output etc. allow regions to have reserved areas 2024-07-09T16:24:12Z Kimplul kimi.h.kuparinen@gmail.com 2024-07-09T16:24:12Z urn:sha1:89d7cf197b2cae130565467bdfad5d5ef5fed2dd + A reserved area is an area at the start of the region that should not be used unless explicitly asked for, for example null pages. As such, a small correction to my previous commit message: There's no danger in not locking req_mem() etc, as a null page will only be allocated when explicitly asked for.