Choose a topic. Each route starts with a reading and gives you an observation you can use to check what you learned.
- From a C call to a Linux system call
- Investigate a slow Linux program
- From a CAN frame to a capture and a bench
From a C call to a Linux system call
Prerequisites: Basic C, pointers, and compilation. Use Linux and a C compiler for the experiment. The ABI explorer also works in the browser.
- Guides · Use the GCC and Clang migration guide to identify compiler and library differences.
- Execmap · Compare x86-64 and AArch64 argument locations for one C function in the function ABI guide. Follow
preadthrough libc and into the kernel in the system call walkthrough. - Syscall · Look up the architecture-specific number and arguments in the
pread64reference.
Outcome: Explain why the same offset appears in rcx at function entry and r10 at system call entry on Linux x86-64.
Investigate a slow Linux program
Prerequisites: Basic C and shell use. Kernel measurements require a suitable Linux host, tools, and permissions.
- Guides · If you need a test environment, start with ARM64 Linux on Apple Silicon.
- Execmap · Use the performance analysis introduction to distinguish on-CPU time from waiting. Calculate elapsed and thread CPU time from raw records in the timing lab.
- Execmap and Syscall · Trace the slow program that barely uses the CPU and look up the observed
futexcall for your architecture.
Outcome: Identify which measurement supports an explanation based on CPU work or waiting.
From a CAN frame to a capture and a bench
Prerequisites: A browser suffices for frame and sample capture inspection. The vcan step uses a compatible Linux host, and the hardware step uses a separate bench setup.
- Wire · Read identifiers and data lengths in the CAN and CAN FD reference. Open an example in the capture analyzer and compare observed intervals for one identifier.
- Wire · Run the virtual CAN experiment to collect a log on Linux. This step observes SocketCAN and a virtual interface.
- Pin Atlas and Wire · For the hardware step, cross-check the Raspberry Pi 4 pin map against the module, voltage, and wiring requirements of the MCP2515 lab.
Outcome: Explain the interval you measured from a capture and which properties require a physical bus measurement.
What each site covers
- Main site · Technical articles, projects, and learning routes.
- Guides · Environment setup, tools, and workflows for Linux, C++, Docker, and virtualization.
- Execmap · Compiled program behavior, ELF loading, function ABIs, and runtime experiments.
- Syscall · System call numbers, arguments, and the Linux kernel ABI by architecture and release.
- Wire · Network protocol headers, bus frames, capture analysis, and SocketCAN experiments.
- Pin Atlas · Board and package pin maps, pin functions, electrical conditions, and wiring plans.