kmi/tests/common/test.h, branch master ACTIVE - Kernel with migrating threads as IPC https://metanimi.dy.fi/cgit/kmi/atom?h=master 2026-01-25T13:07:04Z allow reading fdt in tests 2026-01-25T13:07:04Z Kimplul kimi.h.kuparinen@gmail.com 2026-01-25T13:07:04Z urn:sha1:e8a7fe3bd5c40168d531a6a4f00a7417a278d58c add some basic benchmarks 2024-08-30T15:56:49Z Kimplul kimi.h.kuparinen@gmail.com 2024-08-30T15:56:49Z urn:sha1:1a2e1fff7ce4b8fd8db46549d81e71e76b842da3 improve killing processes/threads, test 2024-08-26T15:51:10Z Kimplul kimi.h.kuparinen@gmail.com 2024-08-26T15:51:10Z urn:sha1:b25156373cd89792b1c457b77699bb7f9beb430d + Remove sys_kill() as we should be using a two-stage process where a thread is first orphaned by sys_detach(), and then the thread itself calls sys_exit() after it has done all necessary cleanup in init. add ipc_notify testcase, remove ipc_ghost 2024-08-22T11:57:14Z Kimplul kimi.h.kuparinen@gmail.com 2024-08-22T11:57:14Z urn:sha1:c3ea570bae8f7daeac8e0614a958e983fcf9940e + A bit easier to implement just ignoring the ipc_resp() arguments than try to enforce that a notification is exited from by ipc_ghost(), especially in cases where the root process has been killed. add basic ipc-req test 2024-08-21T21:08:46Z Kimplul kimi.h.kuparinen@gmail.com 2024-08-21T21:08:46Z urn:sha1:4168cca8124acdbd1866eb87810efe1cfe16903c add ipc_tail() 2024-07-18T14:39:15Z Kimplul kimi.h.kuparinen@gmail.com 2024-07-18T14:39:15Z urn:sha1:f9e23e6e41068d63d42f950941c3d2fc155ef21c + ipc_kick() does a forward and a tail at the same time The idea with ipc_tail() is to allow 'trusted' calls, so for example a process is not allowed to willy-nilly open a file, as it has to go via init(), making the eid 1. This way the receiver can know that the request has gone through init() and can open up a new connection (file, whatever) after which requests from that pid/tid are allowed without init() intervention 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.