kmi/src/pmem.c, branch masterACTIVE - Kernel with migrating threads as IPChttps://metanimi.dy.fi/cgit/kmi/atom?h=master2024-10-30T00:18:12Ztests pass2024-10-30T00:18:12ZKimplulkimi.h.kuparinen@gmail.com2024-10-30T00:18:12Zurn:sha1:e7b5881903ad81efee63966e7d2c42524d465dfcmost of the way to passing tests2024-10-29T22:57:33ZKimplulkimi.h.kuparinen@gmail.com2024-10-29T22:57:33Zurn:sha1:44a73ecab6e91519627786a5101cd4f1a2f2b0d7add magic assert2024-08-26T20:18:05ZKimplulkimi.h.kuparinen@gmail.com2024-08-26T20:18:05Zurn:sha1:280e963e1334a21778e2f257fe09daa4890074a1fix memory leaks destroying threads2024-08-26T20:00:55ZKimplulkimi.h.kuparinen@gmail.com2024-08-26T20:00:55Zurn:sha1:3f194f1c7264945a63b0018b159cc83bd9385c59add malloc test2024-08-21T20:31:48ZKimplulkimi.h.kuparinen@gmail.com2024-08-21T20:31:48Zurn:sha1:97ffab0a8472981b927d0f4e81bb72f6ecd69b86fix LLVM2024-07-08T15:04:03ZKimplulkimi.h.kuparinen@gmail.com2024-07-08T14:43:59Zurn:sha1:e134202611a50b358c147c92bfb8a7f443030b8b
+ Anything extern is right out as LLVM doesn't produce correct code for
them. Maybe if I added some extra attributes but I'm skeptical.
Replaced with static variables and getters/setters.
+ Inline ASM is apparently a bit buggy, so use an assembly stub when jumping to init.
+ Minimize work done in main() to minimize chance of LLVM doing something silly.
Still not 100% certain that I shouldn't just write the main() as an assembly stub
in arch/riscv64 to be absolutely sure everything works as intended.
+ Make .kernel.start section SHF_ALLOC, otherwise lld complains about
pc-relative addressing
Probably some other stuff as well that I'm forgetting right now. But at least with
LLVM14 LTO seems to work, which is pretty cool?
simplify assertions2024-07-07T04:02:46ZKimplulkimi.h.kuparinen@gmail.com2024-07-07T04:02:46Zurn:sha1:b97967ab660243b723f246db03c2e4a82e125f3f
+ No real point having multiple different levels of assertions, just say
you assert something and be done with it
smp now seems to work2024-07-07T04:00:43ZKimplulkimi.h.kuparinen@gmail.com2024-07-07T04:00:43Zurn:sha1:122374c362ba8bb9082385da3c82e264ab594f15
+ Had some minor issues with a wraparound of size_t that effectively
meant that some regions were allocated twice. Also, booting should be
a bit more reliable now, turned out that the previous iteration of the
booting was just accidentally working due to the kernel being placed
'close enough' in RAM to where it was linked to. Fixed by allocating a
vmem of O1 that maps the kernel to a 2MiB boundary at boot, pretty
nifty.
core bringup + various warnings2024-07-06T20:37:11ZKimplulkimi.h.kuparinen@gmail.com2024-07-06T20:37:11Zurn:sha1:3fedbb6e1f849c5e0a4033d68201d60c2fc48121
+ dbg_fdt() is apparently broken, possibly due to UB or something, but
it causes some issues with optimizations enabled. Remove it
temporarily
add RAM usage counting2024-07-06T19:08:50ZKimplulkimi.h.kuparinen@gmail.com2024-07-06T19:08:50Zurn:sha1:3528f88fc36df6964c0efed784ae223cfe93544e
+ Slightly more overhead but will help track down possible memory leaks
in the future. Could also add in a flag for turning off/on but I don't
think the difference in performance is that significant.