MEMORY BOUNDARIES
See how address regions separate privileged kernel memory, device registers, user space, and I/O.
GHOSTKERNEL / SYSTEMS LAB /// SIM BUILD 0.1
ENTER THE
GHOST MACHINE.
A haunted little computer with nothing behind the curtain. Explore memory, wake a device, and watch every system call leave a trace.
◎SEALED SANDBOXDeterministic simulation · no host access · no code execution
GKCORE / 00
KERNEL SPACE RX0x0000SYS_CALL READYDEVICE BUS / SIMULATED+
+
CORE STATEDORMANT
ADDRESS SPACE64 KB SIMULATED
VIRTUAL DEVICES01 ISOLATED
TRACE EVENTS003
SIM CLOCK00:00:00
01 / LIVE SIMULATION
THE DEVICE CHAMBER
LOCAL SANDBOX NO NETWORK
▤ MEMORY MAP64 KB / 4 REGIONS
0x
REGION INSPECTORKERNEL TEXT
Privileged instruction space. Readable by the model, sealed against writes.
PRIVILEGEDDEVICEUSERI/O
◈ DEVICE_01 / WAKE RELAYSIM-0A
ZSLEEP
DW / VIRT01
∿
+
DEVICE STATUSSLEEPINGAwaiting simulated syscall
INTERRUPTIRQ 04
POWER0.0 W
BUSVIRTUAL
⌁ SYSCALL TRACE LIVE
[boot]
GhostKernel simulator initialized.
[mmu]
64 KB virtual address space mapped.
[ready]
Awaiting first system call.
TRACE IS LOCAL TO THIS TAB
02 / UNDER THE HOOD
SMALL MACHINE. BIG IDEAS.
A safe model for the invisible rules that keep a real operating system alive.
THE SYSTEM CALL
Follow a controlled request as it crosses from a user program into the simulated kernel.
VIRTUAL HARDWARE
Wake and idle a tiny relay. Its state changes only inside this teaching model.
SAFE BY DESIGN
No compiler, host calls, uploaded code, or privileged execution. The trace is deterministic and bounded.
READY TO READ THE MACHINE?
TAKE IT TO THE WORKBENCH.
Explore the C lesson and inspect its simulated syscall from the full-size editor.