Hobby operating system for x86_64
Go to file
Bananymous f8261c60c0 Kernel: Rewrite the whole scheduler and re-architecture SMP handling
Change Semaphore -> ThreadBlocker
  This was not a semaphore, I just named it one because I didn't know
  what semaphore was. I have meant to change this sooner, but it was in
  no way urgent :D

Implement SMP events. Processors can now be sent SMP events through
IPIs. SMP events can be sent either to a single processor or broadcasted
to every processor.

PageTable::{map_page,map_range,unmap_page,unmap_range}() now send SMP
event to invalidate TLB caches for the changed pages.

Scheduler no longer uses a global run queue. Each processor has its own
scheduler that keeps track of the load on the processor. Once every
second schedulers do load balancing. Schedulers have no access to other
processors' schedulers, they just see approximate loads. If scheduler
decides that it has too much load, it will send a thread to another
processor through a SMP event.

Schedulers are currently run using the timer interrupt on BSB. This
should be not the case, and each processor should use its LAPIC timer
for interrupts. There is no reason to broadcast SMP event to all
processors when BSB gets timer interrupt.

Old scheduler only achieved 20% idle load on qemu. That was probably a
very inefficient implementation. This new scheduler seems to average
around 1% idle load. This is much closer to what I would expect. On my
own laptop idle load seems to be only around 0.5% on each processor.
2024-07-22 00:33:50 +03:00
.vscode Kernel: Fix sse state saving 2024-07-16 23:15:11 +03:00
BAN BAN: If format string is started with space, numbers are padded with it 2024-07-19 21:39:31 +03:00
assets Update README.md 2023-08-31 17:54:12 +03:00
bootloader BuildSystem: Move all userpace libraries under the userspace directory 2024-06-18 13:14:35 +03:00
kernel Kernel: Rewrite the whole scheduler and re-architecture SMP handling 2024-07-22 00:33:50 +03:00
ports ports: Compile with multiple jobs and fix curl install query 2024-07-16 15:04:46 +03:00
script Kernel: Fix USB code 2024-07-15 11:48:48 +03:00
toolchain BuildSystem: Cleanup CMake code to allow libc only installation 2024-06-21 01:45:14 +03:00
userspace Userspace: Pprogram template and loadfont mark install as optional 2024-07-21 17:41:40 +03:00
.gitignore BuildSystem: using sysroot doesn't need root privileges anymore! 2023-11-04 17:50:43 +02:00
.gitmodules Kernel: Remove lai as a dependecy 2024-04-10 04:39:48 +03:00
.pre-commit-config.yaml General: Add simple contribution guide lines 2024-05-20 20:44:34 +03:00
CMakeLists.txt BuildSystem: Cleanup CMake code to allow libc only installation 2024-06-21 01:45:14 +03:00
LICENSE General: Rename LICENCE -> LICENSE 2024-04-03 15:59:30 +03:00
README.md README: update discord link 2024-07-16 21:10:32 +03:00
base-sysroot.tar.gz Base: Add /var/www with dummy index.html 2024-07-02 21:34:32 +03:00
bos BuildSystem: Add bos short hand for building with zsh completions :) 2023-10-28 22:23:29 +03:00

README.md

banan-os

This is my hobby operating system written in C++. Currently supports x86_64 and i686 architectures.

You can find a live demo here

Features

General

  • Ring3 userspace
  • SMP (multiprocessing)
  • Linear framebuffer (VESA and GOP)
  • Network stack
  • ELF executable loading
  • AML interpreter (partial)
  • ELF dynamic linking
  • Graphical desktop
  • copy-on-write memory

Drivers

  • NVMe disks
  • ATA (IDE, SATA) disks
  • E1000 and E1000E NICs
  • PS2 keyboard (all scancode sets)
  • PS2 mouse
  • USB
  • virtio devices (network, storage)

Network

  • ARP
  • ICMP
  • IPv4
  • UDP
  • TCP (partial and buggy)
  • Unix domain sockets

Filesystems

  • Virtual filesystem
  • Ext2
  • FAT12/16/32
  • Dev
  • Ram
  • Proc
  • Sys
  • 9P

Bootloader support

  • GRUB
  • Custom BIOS bootloader
  • Custom UEFI bootloader

screenshot from qemu running banan-os

Code structure

Each major component and library has its own subdirectory (kernel, userspace, libc, ...). Each directory contains directory include, which has all of the header files of the component. Every header is included by its absolute path.

Building

Needed packages

apt (tested on ubuntu 22.04)

# apt install build-essential git ninja-build texinfo bison flex libgmp-dev libmpfr-dev libmpc-dev parted qemu-system-x86 cpu-checker

pacman

# pacman -S --needed base-devel git wget cmake ninja parted qemu-system-x86

Compilation

To build the toolchain for this os. You can run the following command.

NOTE: The following step has to be done only once. This might take a long time since we are compiling binutils and gcc.

./bos toolchain

To build the os itself you can run one of the following commands. You will need root access for disk image creation/modification.

./bos qemu
./bos qemu-nographic
./bos qemu-debug
./bos bochs

You can also build the kernel or disk image without running it:

./bos kernel
./bos image

To build for other architectures set environment variable BANAN_ARCH=arch (e.g. BANAN_ARCH=i686).

To change the bootloader you can set environment variable BANAN_BOOTLOADER; supported values are BANAN (my custom bootloader) and GRUB.

To run with UEFI set environment variable BANAN_UEFI_BOOT=1. You will also have to set OVMF_PATH to the correct OVMF (default /usr/share/ovmf/x64/OVMF.fd).

If you have corrupted your disk image or want to create new one, you can either manually delete build/banan-os.img and build system will automatically create you a new one or you can run the following command.

./bos image-full

I have also created shell completion script for zsh. You can either copy the file in script/shell-completion/zsh/_bos to /usr/share/zsh/site-functions/ or add the script/shell-completion/zsh to your fpath in .zshrc.

Contributing

As the upstream is hosted on my server https://git.bananymous.com/Bananymous/banan-os, please contact me about account creation (email, discord) and I will add a account for you. This is done to limit the people with access to the server.

As this is mostly a learning experience for me, I would appreciate if you first contacted me about adding new features (email, discord, issue, ...). Bug fixes are always welcome!

Commit message should be formatted followingly

  1. First line is of the form "Subject: Description", where Subject tells the area touched (Kernel, Shell, BuildSystem, ...) and Description is brief description of the change done. First line should fit fully in 70 characters.
  2. Body of the message should further describe the change and reasoning behind the change.

All commits should pass the pre-commit hook defined in .pre-commit-config.yaml. For instructions on how to setup pre-commit, please see https://pre-commit.com/#install.