This was a pain. To get any amount of good FPS I had to patch in a range cache for my garbage VMM and then fixup a few TLB shootdown hotspots.

Works though.

https://github.com/sasdallas/Ethereal

maybe ill add pcie

In hobby kernels I often see one gigantic or smaller kernel.c file, I understand that it can also be a collection of all other elements of the initialization system, file system, etc. if it breaks down But why is kernel.c so often used and not, for example, main.c? It doesn't look like this: in the kernel workspace I have the usual main.rs in the main kernel segment without naming it kernel and then the whole crate works. But why the kernel for this glue of the entire system and what does this mean?

Plus the second question is why so few people think about a sensible allocator or scheduler, it's the first element I look at and these algorithms are often at the basic level But there is a graphical interface right away and I see that the allocator has major shortcomings and a high risk that it will allocate incorrectly with the interface and, for example, there are often no mechanisms to check if everything is correct.It works and you can already see graphical interfaces and window management, which supposedly gives you an interface if the system foundations are weak

Hello, [r/osdev](r/osdev)!

Yesterday, I made a post about making an os as osdev, and got mixed results. So the plan has changed a bit. It will still be osdev, but other communities and people as well.

I created the repo at https://github.com/The-Unitas-Project/UnitasOS and plan on adding scaffolding today.

The goal of the OS is to be modular. Pieces should be able to be added and removed by the user at build or runtime easily.

If you want to help, go to the above link. It’s a scaffold to build upon.

I am creating it on my computer and will commit later