Aren/haiku

Go to file

Augustin Cavalier d0c34f9331 kernel/debug: Invoke cpu_pause in trap_cpu_in_kdl. This is the loop that runs on all CPUs besides the one actually running the kernel debugger. It's functionally a spin-loop around a few different variables, and so it should be safe to use cpu_pause() here, just as real spinlocks do. (cpu_pause() just runs a "pause" or equivalent instruction, it doesn't use the CPU-idle modules, which indeed may be unsafe to use in KDL.) A glance at FreeBSD seems to indicate they also do this when their kernel debugger is active. Seriously improves power consumption while KDL is active: even running in a VM with only a few cores, there would be obvious fan spin-up when entering KDL. After this change, there's barely any at all (while overall CPU usage % remains basically identical.)		2023-09-23 14:07:17 -04:00
3rdparty	3rdparty: Fix revision check	2023-06-22 10:02:29 -05:00
build	ArchitectureRules: Disable autovectorization for the kernel (for now.)	2023-09-22 16:27:37 -04:00
data	Update translations from Pootle	2023-09-23 08:20:09 +00:00
docs	docs: document the steps to update GCC buildtools	2023-08-12 07:59:29 +01:00
headers	headers/compatibility/bsd: Update headers to remove BSD advertising clause.	2023-09-21 18:38:10 -04:00
src	kernel/debug: Invoke cpu_pause in trap_cpu_in_kdl.	2023-09-23 14:07:17 -04:00
.editorconfig
.gitignore	gitignore: Add Visual Studio Code and IntelliJ IDEA configuration directories	2021-05-31 20:15:44 +00:00
.gitreview	gerrit: Add .gitreview config	2018-01-04 00:04:02 -06:00
configure	cross_tools: allow specifying a custom sysroot path	2022-06-05 09:08:20 +00:00
Jamfile	build-packages: update to the latest packages	2023-08-05 11:52:00 +00:00
Jamrules	Revert "Jamrules: Include the UserBuildConfig before processing repositories."	2019-09-15 17:33:36 +02:00
lgtm.yml	lgtm.yml: disable Wformat-diag when building gcc	2021-12-14 06:06:41 +00:00
License.md
ReadMe.Compiling.md	Readme.Compiling.md: Use new build profiles	2023-01-15 16:02:14 +00:00
ReadMe.md	ReadMe: Add Getting Involved link	2021-06-13 21:06:58 +00:00

ReadMe.md

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.