summaryrefslogtreecommitdiffstats
path: root/CONTEXT.md
diff options
context:
space:
mode:
authorsalmonik <salmonik@tuta.io>2026-08-01 22:28:34 +0200
committersalmonik <salmonik@tuta.io>2026-08-01 22:28:34 +0200
commitab7d87bcde31c1681ea09c30534dde840a58d6fa (patch)
tree42eed2c86663cf6ecfa3507ca46399e31b441c99 /CONTEXT.md
parentrsboot: track latest upstream HEAD (92367a8) instead of pinned ee1c85b (diff)
downloadrs-dos-ab7d87bcde31c1681ea09c30534dde840a58d6fa.tar.gz
rs-dos-ab7d87bcde31c1681ea09c30534dde840a58d6fa.zip
rsnix v0.5.2: fault diagnostics + real-hardware scroll-crash hardening
The real-hardware scroll crash (white bands + instant freeze, QEMU-clean) was invisible because the only trace was a single serial line on machines with no serial console. This makes every crash self-identifying and hardens the real-hardware failure surfaces: - Every CPU exception vector 0-31 now has an IDT entry (macro-generated stubs; 8/14 keep their IST stacks). A fault in the shell prints a white-on-red band to the framebuffer via gop::dump_lines (raw fb writes bypassing the vt, fully clamped) plus a parseable serial line: '!!! <kind> vec=N err=… rip=… cr2=… rsp=… rflags=… task=N "name"', then halts — instead of converging to a cryptic double fault. Background-task faults abort the task as before. - Boot log now reports the authoritative post-SetMode geometry: 'gop: fb base=… size=… pitch=… WxH bpp=… bgr=…', so the next real machine's report identifies whether pitch*height exceeds the mapping. - Framebuffer writes (clear, push_rect, shift_up_n bulk push, cursor overlay) are clamped to the firmware's framebuffer_size: a pitch- padded mode degrades to a truncated view instead of faulting past the mapping. - The GOP framebuffer region is excluded from the page allocator (and subtracted from the heap's conventional-region pick) even when the firmware lists it as ConventionalMemory — kernel allocations can never overwrite the display again. The GOP protocol is located and peeked before the memory map is captured so the exclusion is known at heap-init time. - Shell gains a hidden 'fault' command (deliberate unmapped write) and 'make test-fault' verifies the dump: vec=14, cr2=0x400000000000, task=0, halt — no triple fault. All other suites re-pass. - CONTEXT.md: fault-dump format documented for real-hardware reports.
Diffstat (limited to '')
-rw-r--r--CONTEXT.md23
1 files changed, 19 insertions, 4 deletions
diff --git a/CONTEXT.md b/CONTEXT.md
index 375bf57..f068035 100644
--- a/CONTEXT.md
+++ b/CONTEXT.md
@@ -113,10 +113,13 @@ Workspace version is `a.b.c` (single version for all crates):
113 113
114Bump the workspace version in the root `Cargo.toml` when a change of 114Bump the workspace version in the root `Cargo.toml` when a change of
115that class lands — do not leave the version to drift. Current: 115that class lands — do not leave the version to drift. Current:
116`0.5.1` — the GUI era landed with 0.5.0 (graphics layer + cursor 116`0.5.2` — the GUI era landed with 0.5.0 (graphics layer + cursor
117compositor) and the canvas was fixed at 800×600 as a `c` bump; a 117compositor); 0.5.1 fixed the canvas at 800×600; 0.5.2 added fault
118future major GUI overhaul (graphics windows beyond the text surface) 118diagnostics (screen + serial dumps for every CPU exception) and
119would be the `a` bump (1.0.0). 119real-hardware hardening (framebuffer-size clamping, fb-region exclusion
120from the allocators, authoritative fb geometry logging). A future
121major GUI overhaul (graphics windows beyond the text surface) would be
122the `a` bump (1.0.0).
120 123
121## Project layout 124## Project layout
122 125
@@ -388,6 +391,18 @@ Workspace of four crates, all built for the `x86_64-unknown-uefi` target:
388 hardware pushes only 24 bytes at same privilege, so the extra 391 hardware pushes only 24 bytes at same privilege, so the extra
389 fields are inert there; the synthetic frames set them 392 fields are inert there; the synthetic frames set them
390 explicitly either way. 393 explicitly either way.
394- `interrupts`/`sched` fault dumps (0.5.2): every CPU exception
395 vector 0-31 has an IDT entry (macro-generated stubs; 8/14 keep
396 their ISTs). Any fault in the shell (task ≤ 1) prints a
397 white-on-red band via `gop::dump_lines` (raw fb, bypasses vt,
398 clamped) *and* a parseable serial line — `!!! <kind> vec=N
399 err=… rip=… cr2=… rsp=… rflags=… task=N "name"` — then halts;
400 faults in background tasks abort the task instead. Real
401 hardware has no serial console, so the screen band is how a
402 crash reports itself; a non-canonical write shows vec=13 (GP,
403 cr2=0), an unmapped canonical address shows vec=14 with cr2=
404 the address. `fault` shell command + `make test-fault` verify
405 the path.
391- Panic handling: a task panic (or guard-page overflow) is caught, 406- Panic handling: a task panic (or guard-page overflow) is caught,
392 logged as `sched: task N "name" panicked: …`, the task is marked 407 logged as `sched: task N "name" panicked: …`, the task is marked
393 Done, and the scheduler switches away — the shell keeps running. 408 Done, and the scheduler switches away — the shell keeps running.