fbos/test, branch main

test: Remove asserts on specific entry addrs

2024-12-03T07:00:53Z

These asserts where needed when I was iterating on the initrd handling code, but they are admittedly too specific and prone to errors. Hence, get rid off them. Signed-off-by: Miquel Sabaté Solà

Remove stack pointer for each process

2024-12-03T06:59:01Z

Since 6132623dbf30 ("Share the same stack everywhere") the same stack is used everywhere. Hence, it's rather pointless for each task to have a pointer to a stack which is the same and that is never read. Signed-off-by: Miquel Sabaté Solà

Simplify the constant on the size of the stack

2024-12-03T06:41:45Z

At the beginning I carried over things from the Linux kernel just in case I would need them in the future. As this project is very much at a stage where I'm already happy with it, let's remove unneeded complexity. Signed-off-by: Miquel Sabaté Solà

Share the same stack everywhere

2024-12-02T20:02:35Z

As documented in the code, we are not implementing any kind of memory protection, so in theory any process (regardless if running in user or kernel space) would be able to tamper with other processes' stack. Hence, don't even pretend that we are separating stacks and share the same global stack everywhere. This simplifies things a bit. Signed-off-by: Miquel Sabaté Solà

Show the detected machine model

2024-11-26T20:43:54Z

Originally I was planning to detect the machine model just in case we needed to do workaround for special cases. But since apparently even VisionFive2 brings its own CPU frequency base on DT, this is not even needed. Hence, fetching the model is now a cool message being shown on boot. Signed-off-by: Miquel Sabaté Solà

test: Add a DT test for a VisionFive2 board

2024-11-26T20:42:50Z

Signed-off-by: Miquel Sabaté Solà

dt: Fetch the CPU frequency as well

2024-11-26T12:59:54Z

If the 'timebase-frequency' property is available under the 'cpus' node from the DTB blob, it makes sense to try to fetch this value from there instead of hardcoding it. For other use-cases, where this information is not available through DT (e.g. ACPI on the VisionFive2 board), we will have to hardcode it with a default value even if it's not the proper one. Signed-off-by: Miquel Sabaté Solà

tests: Only test initrd addresses on debug

2024-11-25T06:45:26Z

In initrd tests, and in general, we only need to check that the function did something. As in, that it set the entry addresses somewhere and did not leave them NULL. This is going to be performed from now on on CI and regular tests. And, just if you want to go the extra mile, we will run specific tests that check on memory addresses but that are not guaranteed to work. This is to be replaced in the future by having some proper debugging output. As in, having a message at kernel boot time specifying the addresses being used among other info. This needs a more complex printk utility, of course. Signed-off-by: Miquel Sabaté Solà

test: Fix test on initrd

2024-11-24T22:55:25Z

This was broken since I first introduced the test on initrd on 40ffc517e20c ("Initial parsing of the provided initrd file") but it always was as a work in progress test. Now that the initrd parsing has separation of concerns with the global 'tasks' variable since f4986dab75fa ("Accept tasks as a parameter on initrd extraction"), we can have a proper test written for this. Signed-off-by: Miquel Sabaté Solà

Accept tasks as a parameter on initrd extraction

2024-11-24T22:27:13Z

This allows this functionality to be properly extracted for unit tests. Signed-off-by: Miquel Sabaté Solà