bdc925d275a471996dccba79923791ca06bd3be1
Previously, the kernel used the regular FS segment for Thread-Local Storage. The problem however, is that userspace code also uses FS for TLS, meaning that the kernel would have to switch the FS segment between user and kernel, _upon every syscall_. This is obviously suboptimal for performance (especially with fast syscalls such as futex, nanosleep, or yield). I had to search LLVM for hours, just to find out that the insertion of the memory load with FS was actually done in the linker, so I added a flag for that. I haven't done any proper benchmarking, but the boot process seems to have gotten much faster!
kernel
Redox OS Microkernel
Debugging the redox kernel
Running qemu with the -s flag will set up qemu to listen on port 1234 for
a gdb client to connect to it. To debug the redox kernel run.
make qemu gdb=yes
This will start a VM with and listen on port 1234 for a gdb or lldb client.
gdb
If you are going to use gdb, run the following to load debug symbols and connect to your running kernel.
(gdb) symbol-file build/kernel.sym
(gdb) target remote localhost:1234
lldb
If you are going to use lldb, run the following to start debugging.
(lldb) target create -s build/kernel.sym build/kernel
(lldb) gdb-remote localhost:1234
Debugging
After connecting to your kernel you can set some interesting breakpoints and continue
the process. See your debuggers man page for more information on useful commands to run.
Description
RedBear Operating System, based on RedoxOS. Licenced under MIT license.
https://redbearos.org
Languages
Rust
98.8%
Assembly
0.6%
Linker Script
0.5%
Makefile
0.1%