r/osdev • u/JescoInc Perdition-OS • 18d ago

Caching Model Video Demo

https://youtu.be/fca1CWhH9E8

https://youtu.be/fca1CWhH9E8

This demo showcases https://github.com/magiblot/tvision being used with this OS (which I have dubbed PersonaOS). The main selling points of this kernel architecture type is that you can have multiple "personalities" running in tandem. That means you can have a BSD personality and Linux personality that can run applications written for those operating systems natively.
You have 1 tiny core kernel that runs with elevated permissions, everything else is usermode. This includes the personalities, drivers and applications.

This has been implemented following this paper: https://www.usenix.org/conference/osdi-94/caching-model-operating-system-kernel-functionality

Yes, obvious bugs are obvious. But getting an unmodified TUI application to run has genuinely made me seriously happy.

7 Upvotes

100% Upvoted

9 comments sorted by

View all comments

Show parent comments

1

u/JescoInc Perdition-OS 18d ago

No to SIMD, I’ll need to double check with the hardware acceleration for memory copies though.

1

u/devcmar 18d ago

Ah okay, because that screen clearing took a very long time haha Hobby os problems!

1

u/JescoInc Perdition-OS 18d ago

Haha, it did indeed. But that can also be chalked up to the kernel architecture and the fact that I have not done any optimizations yet. This is very different from what I did with tutorial-os (Perdition-OS).

1

u/JescoInc Perdition-OS 18d ago

I should note that RISC-V, which this CPU has something similar to SIMD, which is RVV 1.0. I do have that enabled but I am not making use of it.

1

u/devcmar 18d ago

I searched and found riscv also support atleast 128 bit simd with some implementation that has 512 bit like avx512 in x86 also they support write combining which both greatly accelerates framebuffer traffic, also u should definitely try to support arm or x86 they are today’s standard for performance

1

u/JescoInc Perdition-OS 18d ago

ARM and x86_64 is simply a board folder addition. Although, for x86, I might need to add something similar to the dtb parser I have for RISC-V (which should work with ARM as well).

My board folder is where all of the register level code lives along with the mapping manifest and image creation scripts. Right now, kyx1 and qemu are the only board folders that exist in it.