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 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 | //! 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.
//!
//! Threads that run user code (processes, see process.rs) additionally carry
//! an address space (CR3) and a kernel stack top. On every switch the
//! scheduler loads the next thread's CR3 and points the TSS's RSP0 and the
//! syscall entry at its kernel stack, so interrupts and syscalls from ring 3
//! land on the right stack.
//!
//! Blocking: a thread waiting for something (keyboard input, a child
//! process, a pipe, a timeout) is marked `blocked` and the scheduler skips it
//! until someone calls `wake` (or its sleep deadline passes). That's what
//! `WaitQueue` is for. If *every* thread is blocked, the CPU idles with `hlt`
//! until an interrupt wakes somebody up.
//!
//! Locking rule (single CPU!): any lock that is also taken with interrupts
//! *off* (the scheduler's, a wait queue's, a pipe buffer's...) must *always*
//! be taken with interrupts off. Otherwise a thread could be preempted while
//! holding it, and the next thread would spin on it forever, unable to be
//! preempted itself.
//!
//! 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 crateProcess;
use ;
use global_asm;
use Mutex;
use interrupts;
use Cr3;
use PhysFrame;
/// 64 KiB per thread stack. There's no guard page (stacks are plain heap
/// memory), so overflowing one silently overwrites whatever lies below it.
/// We at least *detect* that afterwards: the lowest 8 bytes hold
/// `STACK_CANARY`, checked whenever the scheduler switches away from a
/// thread. (16 KiB was enough until syscalls went through the FAT driver:
/// unoptimized debug builds use big stack frames.)
const STACK_SIZE: usize = 64 * 1024;
const STACK_CANARY: u64 = 0x5AFE_57AC_C0DE_CAFE;
static SCHEDULER: = new;
/// Start a new kernel thread running `entry`. Needs the heap.
/// Start a thread for `process`: runs `entry` (in the kernel) with the
/// process's address space `cr3` active; `entry` then drops to ring 3.
/// On first use, register the code that's running right now (the boot/main
/// thread) as thread 0. Its rsp is filled in the first time we switch away.
/// 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.
/// Give up the rest of this time slice (also callable outside interrupts).
/// The process the running thread belongs to, if any.
/// End the running thread: mark it finished and switch away for good.
/// (Its stack is kept: we're still running on it until the switch.)
!
/// Name of the running thread (for printing).
/// Id of the running thread (its index in the thread list; ids are never reused).
/// Make thread `id` runnable again (no-op if it isn't blocked).
/// Mark the running thread blocked, then run other threads until somebody
/// wakes it. Must be called with interrupts *off* (so a wake-up can't slip in
/// between the caller checking its condition and us blocking); returns with
/// interrupts still off.
/// Sleep for `ticks` timer ticks (~55 ms each). The thread is *blocked*
/// meanwhile, so it costs no CPU time; the scheduler wakes it up.
/// Threads waiting for some event (like a Linux `wait_queue_head_t`).
///
/// Usage: `queue.wait_until(|| condition)` blocks until the closure returns
/// `Some(value)`; whoever makes the condition true calls `queue.wake_all()`.
/// The closure runs with interrupts off, so it must be quick and only touch
/// locks that follow the locking rule at the top of this file.
// --- 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" !
|