Discover and read the best of Twitter Threads about #osdev
Most recents (2)
Systems research is hard and time consuming. Let's talk about that using this bug in Twizzler that I just squashed as an example.
It can be hard to make “research progress" in the face of these things.
#osdev is fun, I promise! Let's start with the bug itself... (0x0/n)
It can be hard to make “research progress" in the face of these things.
#osdev is fun, I promise! Let's start with the bug itself... (0x0/n)
So the bug was this: Twizzler would boot, I would run “for i in {1..10}; do ls & done”, and then hit enter. The system would freeze.
This ended up being a combination of the scheduler, interrupt handling, userspace drivers, thread exiting, and page-faults. 0x1/n
This ended up being a combination of the scheduler, interrupt handling, userspace drivers, thread exiting, and page-faults. 0x1/n
Here’s what would happen: hitting any key after that for loop would cause an infinite number of page faults. Why? Well, the page-fault handler is supposed to “fix” the state so that the memory access succeeds (or kill the thread). Right? 0x2/n
Thread: After 6 years of #osdev experience, here are my recommendations for trying out making your own Operating System from scratch:
The operating systems development (osdev) wiki is awesome and has the tutorial you should start with: wiki.osdev.org/Bare_Bones
If I still have your attention, you need to read the rest of this thread before starting. You need to read all the instructions carefully!
