vasilito
f7652fc26a
Phase 0c, plan orders #3, #4, #7. P5-context-mod-sched: re-export SchedPolicy from context::mod (one-line change to the use statement). The type is defined in context::context by the previous P7-cache-affine-context commit; this just makes it available as crate::context::SchedPolicy. P8-percpu-sched: adds PerCpuSched struct to percpu.rs with SyncUnsafeCell- wrapped run_queues, balance/last_queue/last_balance_time cells, and take_lock/release_lock methods. Refactors PercpuBlock to embed PerCpuSched as 'sched' field instead of standalone 'balance'/'last_queue' fields. Adds get_percpu_block() helper. P8-percpu-wiring: rewrites src/context/switch.rs to consume PerCpuSched: - select_next_context reads from percpublock.sched.queues() instead of the global RunContextData.set - Initial placement chooses least-loaded CPU via PercpuSched.balance - Load balance trigger fires periodically and migrates contexts between per-CPU queues respecting sched_affinity - Adds pub const fn to access per-cpu sched state safely After this commit, the kernel builds with per-CPU run queues wired into the scheduler. cargo check still has 1 pre-existing unrelated error (src/acpi/fadt.rs:110 type mismatch) that predates the threading work. Combined with the P6-futex-sharding commit, this completes the foundation for Phase 1 (Futex Completeness) and Phase 2 (SMP Scheduling Quality).
Kernel
Redox OS Microkernel
Requirements
nasmneeds to be available on the PATH at build time.
Building The Documentation
Use this command:
cargo doc --open --target x86_64-unknown-none
Debugging
QEMU
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 virtual machine with and listen on port 1234 for a GDB or LLDB client.
GDB
If you are going to use GDB, run these commands 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 these commands to start debugging:
(lldb) target create -s build/kernel.sym build/kernel
(lldb) gdb-remote localhost:1234
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.
Notes
-
Always use
foo.get(n)instead offoo[n]and try to cover for the possibility ofOption::None. Doing the regular way may work fine for applications, but never in the kernel. No possible panics should ever exist in kernel space, because then the whole OS would just stop working. -
If you receive a kernel panic in QEMU, use
pkill qemu-systemto kill the frozen QEMU process.
How To Contribute
To learn how to contribute to this system component you need to read the following document:
Development
To learn how to do development with this system component inside the Redox build system you need to read the Build System and Coding and Building pages.
How To Build
To build this system component you need to download the Redox build system, you can learn how to do it on the Building Redox page.
This is necessary because they only work with cross-compilation to a Redox virtual machine, but you can do some testing from Linux.
Funding - Unix-style Signals and Process Management
This project is funded through NGI Zero Core, a fund established by NLnet with financial support from the European Commission's Next Generation Internet program. Learn more at the NLnet project page.
