3 ms·
This is awesome very good combination. seL4 is formally verified and then slap a memory safe and performant user-level code on top. More info about L4 micro-ke
by rdtsc 11y ago
This is awesome very good combination. seL4 is formally verified and then slap a memory safe and performant user-level code on top.
More info about L4 micro-kernel:
https://sel4.systems/Info/FAQ/ https://sel4.systems/Info/FAQ/
Now user-level here means drivers as well. So that would be interesting how it would work with Rust. Will it all default to unsafe code and just end up with pointer twiddling and memory overwrites and all the same errors. I hope not.
Currently it seems that the verification mode had DMA turned off and for SMP they run a kernel instance on each core and then send messages to each other via shared memory. That probably means not load balancing or not scheduling?
- anp 11y agoRe: low-level Rust, I've been really enjoying following this series: http://os.phil-opp.com/ http://os.phil-opp.com/ It shows a variety of ways to safely wrap unsafe code and then provide strongly-typed safe interfaces to the hardware, no pointer twiddling required. A particularly good example is the section "Some Clever Solution" in the "Page Tables" post.
- rdtsc 11y agoOoh nice guide. Thanks for the link! I was looking at the printing to screen section: http://os.phil-opp.com/printing-to-screen.html http://os.phil-opp.com/printing-to-screen.html It is so helpful to have the explanation of what is going and why the code looks the way it is, what are some alternatives and why those wouldn't work.
- kibwen 11y agoSorry, I think I downvoted you by accident. HN's mobile interface makes scrolling risky... :)
- dikaiosune 11y agoWe've all been there :).
- cmrx64 11y agoMulticore support + verification is in the works, see https://ssrg.nicta.com.au/publications/nictaabstracts/Peters_DEH_15.abstract.pml https://ssrg.nicta.com.au/publications/nictaabstracts/Peters...