nostr:npub1ytaj77p3h2arscwmuuzgh48e4szkwnlwyval7zqn8sy52hprwjas4fayt9 great idea -- thinking out loud, maybe I could trace some stuff in the kernel, like something in the ext4 filesystem code where it actually flushes the write to disk, or something earlier like when it calls into the interpreter?
nostr:npub1upkp7fd7rc3lrjg23r8gy0wc723vze7mxlx5984ut6zurjzpf5xss4tcwy As far as "Linux spy tools", `bpftrace` is a neat one.
The *really* arcane things happen lower in the stack here. Architecture specific system call ABI, how a trap/syscall instruction triggers a context switch into kernel mode, how the kernel schedules IO operations, sends commands to drivers, how they actually communicate with hardware with mmio/interrupts/DMA/etc.
But then you could have a full length book just on how printing hello world works.
Discussion
No replies yet.