kmi/arch/riscv/common/vmem.c, branch master ACTIVE - Kernel with migrating threads as IPC https://metanimi.dy.fi/cgit/kmi/atom?h=master 2021-12-20T11:29:01Z Revert "still some issues with vmem" 2021-12-20T11:29:01Z Kimplul kimi.h.kuparinen@gmail.com 2021-12-20T11:29:01Z urn:sha1:6b2465318b2dc922de282deea96c1621f7f41039 This reverts commit 69d13626a37e33f31627a1144605a8fb93684d25. still some issues with vmem 2021-12-20T11:12:06Z Kimplul kimi.h.kuparinen@gmail.com 2021-12-20T11:12:06Z urn:sha1:a37974009152b4bf6a2d7ed205a48230f939dd72 + Not sure if I should go with noinit or init, fuck Massive changes to jump to userspace 2021-12-19T15:10:36Z Kimplul kimi.h.kuparinen@gmail.com 2021-12-19T15:10:36Z urn:sha1:9966b49db468de0168c7a455dfb5b4c66c413c4d Some minor changes to virtual memory handling 2021-10-25T16:44:11Z Kimplul kimi.h.kuparinen@gmail.com 2021-10-25T16:40:53Z urn:sha1:7f7b3d61baf46fe358d3f1bd1cb584e0daed3a81 + Should start to think about how virtual memory should be handled efficiently, I'm sort of flailing around and not actually doing anything beneficial. The mapping system I've so far implemented _works_, but it's not good and I'm not happy with it. I might come back and fix/improve it, but I think I'll go ahead and do other things for a while, might give me a better overhead view of what the virtual memory system should do. + TODO: should probably document the memory layout I'm going with at the moment. Initial virtual memory mapping functions 2021-10-19T12:56:26Z Kimplul kimi.h.kuparinen@gmail.com 2021-10-19T12:56:26Z urn:sha1:59a374b0eed4313d1a67e2cdb673a295e79a6494 Start designing vmem framework 2021-10-11T20:18:47Z Kimplul kimi.h.kuparinen@gmail.com 2021-10-11T20:18:47Z urn:sha1:7237d673904d8568a2f9c290a0247c9d1a07c5d2 Renamed [pv]addr_t to [pv]m_t 2021-10-11T11:02:31Z Kimplul kimi.h.kuparinen@gmail.com 2021-10-11T11:02:31Z urn:sha1:ebd34a9ab3809167e16e4107c8e72d1d81faff9c Prepare proper jump to kernel 2021-10-10T20:03:20Z Kimplul kimi.h.kuparinen@gmail.com 2021-10-10T20:03:20Z urn:sha1:d2ff961a2a08229e1f2245e8dba9b2275016133c First jump to virtual memory! 2021-10-01T17:36:15Z Kimplul kimi.h.kuparinen@gmail.com 2021-10-01T17:36:15Z urn:sha1:b30ee14270a44e48167934b9b3923b4280bdc855 + Lots of bughunting to do, probably lots of off-by-one and so on errors, and I make a lot of naive and possibly dangerous assumptions. But cool start nonetheless. Should also come up with some method of exchanging data between the init and actual kernel, probably some struct of some sort. TODO