kmi/arch/riscv64/conf/init.c, branch masterACTIVE - Kernel with migrating threads as IPChttps://metanimi.dy.fi/cgit/kmi/atom?h=master2024-07-09T19:12:27Zstart working on tests2024-07-09T19:12:27ZKimplulkimi.h.kuparinen@gmail.com2024-07-09T19:12:27Zurn: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 areas2024-07-09T16:24:12ZKimplulkimi.h.kuparinen@gmail.com2024-07-09T16:24:12Zurn: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.
allow mapping null page2024-07-09T14:35:56ZKimplulkimi.h.kuparinen@gmail.com2024-07-09T14:35:56Zurn:sha1:298636079d912d0936f8156a609fe74b839c547b
+ User has to 'free' the 0 page before it becomes accessible to mapping.
Probably worth noting that this is likely VERY niche and mainly
concerns stuff like certain kinds of emulators that I'm still
eons from implementing, but still.
Unbacked pages can also be useful for some kinds of notifications,
like 'if someone writes to this page, please report it to me with this
ID' or whatever, I remember seeing some discussion about it somewhere
but that's also not really relevant for the moment.
Most significantly, at least with the current design,
after the null page is freed it becomes available for use to regular req_mem()
calls, so users should probably using locks around memory requests.
That's probably a good idea anyway as internally the kernal has to
lock the virtual memory, and without a scheduler it might cause
threads to spin for a while in the kernel which is rather bad.
add req_page back in as I realized it's useful2024-07-07T18:47:14ZKimplulkimi.h.kuparinen@gmail.com2024-07-07T18:47:14Zurn:sha1:219c27d420fe0abe5515cefc2513c6fe60aafdf9
+ Can be used to pass contiguous memory regions to things like virtio
block devices for implementing disk drivers etc.
make executable entrypoint universal callback2024-07-07T15:12:55ZKimplulkimi.h.kuparinen@gmail.com2024-07-07T15:12:55Zurn:sha1:fe4c623cb9320226866829317cea8ba0c49e7dbc
+ Effectively means that all executables can be called into, but if an
exe doesn't want to deal with anyone else it should just set a flag
like `not_really_a_server` or whatever
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.
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.
pretty massive virtual memory rewrite2024-07-06T15:14:04ZKimplulkimi.h.kuparinen@gmail.com2024-07-06T15:14:04Zurn:sha1:76517486919657ecadda9867125dc6730f29a5b7
+ The system is now a bit simpler and hopefully easier to understand, while also
extending the shared memory to be 1:N, where there is one owner who
may become a zombie while waiting for the N to die.
more complete interrupt handling outline2024-07-02T18:40:10ZKimplulkimi.h.kuparinen@gmail.com2024-07-02T18:40:10Zurn:sha1:8a3452098267e1af127d6c4f1836a9d82cd23f38
+ Still largely untested, should really try to come up with a proper
testsuite, at the moment it's mostly me trying things out in the (as
of yet unreleased) kmx repo
expand notifications into interrupt handlers2024-07-01T20:34:57ZKimplulkimi.h.kuparinen@gmail.com2024-07-01T20:34:57Zurn:sha1:7ad9c01dad7b1b46eced8290b8b991383d648188
+ Terminology is still a bit poor, and will still have to write
documentation + implement ipis properly