8d63c2f657
This has been broken since January 2014, from a change made during the scheduler refactor (527da4ca8a4c008b58da456c01a49dcf16a98fbc). How nobody seems to have figured this out since then, I have no idea, especially since the 32-bit initialization routine had the critical function (x86_get_double_fault_stack) commented out entirely. Even if it wasn't commented out (and it wasn't for 64-bit), it wouldn't have worked, because the double-fault stacks were not allocated until "post-VM", while the TSS is set up during "preboot" (basically just after kernel entry.) We now take care of this by allocating the virtual address for the stacks immediately, and then creating an area for it in the "post-VM" stage. This means that any double-faults which occur before the post-VM stage will just triple-fault, but seeing as all double-faults have been triple-faults for the past decade, that's probably fine. (In order to get a double-fault stack that early, we would probably need to have the bootloader allocate it for us.) This must be working, because it changes #18692 from a triple-fault (instant reboot) into a double-fault KDL.
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.