I'm Hans. I work on GPU systems at a fabless semiconductor company. I care about the boundaries that make a GPU usable as a system: where the driver meets the kernel, where firmware takes over resource management, and where virtual addresses become mappings, residency decisions, and migration.

Areas of focus

  • Driver and kernel integration: module boundaries, kernel interfaces, and resource lifecycles
  • Bring-up and failure analysis: boot stages, firmware handoffs, and locating the layer that actually failed
  • Memory systems: address translation, residency, migration, coherency, and fault handling
  • Systems tooling: tracing, crash evidence, and reproducible debugging workflows

About this site

This site is a public field notebook: compact notes for mechanisms worth remembering and longer explanations when a boundary needs to be followed end to end. It is intentionally static, lightweight, and kept close to the source files.

The views here are my own. I write from public interfaces, upstream sources, and general engineering practice; confidential work stays private.

Elsewhere

Find my public code and repositories on GitHub.