userspace.party

userspace.party / kernelspace

kernelspace

Across the boundary.

Kernel-facing execution, symbols, startup and linker work beside the userspace layer.

API docs crates.io GitHub
no_std kernel boundary symbols freestanding

Its place in the system

kernelspace is the counterpart to userspace when work must cross below the process boundary into kernel-facing execution and symbol integration.

userspace
   │ syscall boundary
   ↓
kernelspace
   ├── kernel symbols
   ├── startup
   └── linker integration

The boundary

Belongs here

  • Kernel-facing execution experiments
  • Kernel symbols
  • Kernel-side startup/linking concerns

Does not belong here

  • Userspace syscalls themselves
  • Generic abstractions
  • Browser presentation
  • Physical simulation

Today

Current surface

  • no_std library surface
  • Kernel symbol work under modules::ksym
  • Freestanding entry/startup assembly
  • Custom linker/build integration

Start here

cargo add kernelspace

Early and intentionally experimental; the kernel-side architecture is still forming.

From abstraction to reality. userspace.party keeps conceptual borders explicit: abstractions in ample, process mechanisms in userspace, machines in computers, human meaning in humans, browser presentation in webspace, and physical-world simulation and control in twins.