How pezfisk/invos works
Project type and purpose
• This is a low-level OS kernel (“InvOS”) written in Rust, following Philipp Oppermann’s blog tutorial. Its goal is to produce a minimal executable that boots on x86_64 hardware or QEMU, sets up the CPU (GDT, interrupt handling), and provides simple I/O (VGA text buffer, serial port).
File structure
• Top-level Rust/Cargo files and toolchain configuration (.cargo/, Cargo.toml, rust-toolchain) define a no_std kernel crate with custom target spec (x86_64-inv.json).
• src/ holds kernel code split into logical modules:
• main.rs – entry point (_start) and high-level init
• gdt.rs – Global Descriptor Table setup
• interrupts.rs – Interrupt Descriptor Table and handlers
• serial.rs – serial port driver interface
• vga_buffer.rs – VGA text buffer driver
• lib.rs – crate root (public exports, panic handler)
• tests/ contains integration tests that run the compiled kernel in QEMU and verify behavior (boot, panic conditions, stack overflow).
README
• Confirms that InvOS strictly follows the tutorial architecture: a bare-metal kernel with CPU initialization, minimal drivers, tests via QEMU. No mention of extra services or layers beyond the kernel itself.
Final advice
• Be exhaustive: break the kernel into as many logical sub-systems as you have modules.
• Both control flow (initialization sequence) and data flow (how output reaches VGA/serial).
• Use layering (hardware at bottom, kernel modules in the middle, tests/tools on the side) so it’s immediately clear where each piece lives and how they interact.