rust-kernel
Rustbelt: a hobby x86_64 kernel written in Rust
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 | //! Preemptive kernel threads (beyond the phil-opp series).
//!
//! Each thread has its own stack. The timer interrupt calls `schedule()`,
//! which picks the next thread round-robin and calls `switch_context` to swap
//! stacks. Threads don't have to cooperate: even `loop {}` gets interrupted.
//!
//! How a switch works (all inside the timer interrupt, interrupts off):
//!
//! thread A running -> timer IRQ -> CPU pushes A's RIP/RSP/RFLAGS (the
//! interrupt frame) on A's stack -> the `x86-interrupt` handler saves the
//! caller-saved registers (rax, rcx, rdx, rsi, rdi, r8-r11) on A's stack ->
//! `schedule()` -> `switch_context(&A.rsp, B.rsp)`:
//! push the callee-saved registers (rbx, rbp, r12-r15) on A's stack
//! save rsp into A.rsp
//! load rsp from B.rsp <- now we're on B's stack
//! pop B's callee-saved registers
//! ret <- returns into B's earlier schedule()
//! ... which returns into B's timer handler, which restores B's caller-saved
//! registers and `iretq`s back to wherever B was interrupted.
//!
//! So a sleeping thread's whole CPU state is simply sitting on its own stack,
//! and all we have to remember per thread is its stack pointer.
//!
//! A *new* thread has never been interrupted, so `spawn` builds a fake stack
//! that looks like `switch_context` saved it, with the "return address"
//! pointing at `thread_trampoline`, which enables interrupts and calls the
//! thread's function.
use ;
use global_asm;
use Mutex;
use interrupts;
/// 16 KiB per thread stack (no guard page! a deep recursion in a thread
/// silently overwrites whatever is below its stack on the heap).
const STACK_SIZE: usize = 16 * 1024;
static SCHEDULER: = new;
/// Start a new kernel thread running `entry`. Needs the heap.
/// Called from the timer interrupt (interrupts disabled, EOI already sent).
/// Switches to the next runnable thread, round-robin. Returns when this
/// thread is scheduled again.
/// Name of the running thread (for printing).
/// Sleep for `ticks` timer ticks (~55 ms each), letting other threads run.
// --- assembly ---------------------------------------------------------------
unsafe extern "C"
// System V calling convention: 1st argument in rdi, 2nd in rsi. A normal
// function call already saved the caller-saved registers, so only the
// callee-saved ones (rbx, rbp, r12-r15) need saving here.
global_asm!;
/// Rust side of a new thread's life.
extern "C" !
|