Linux中ps aux为何不显示PID=0的空闲进程？该进程初始化后是否退出？

Great question—this gets into some kernel-level nuances that aren't obvious from standard user-space tools like ps. Let's break this down step by step:

What Exactly Is PID=0? #

PID=0 is the idle process (you might see it called the swapper in older Linux kernel docs). It’s the very first "process" the kernel creates during boot, even before PID=1 (systemd or init, the user-space init process). Unlike regular processes, it’s not a user-space program—it lives entirely in the kernel, and its only job is to run when no other processes need the CPU. It essentially loops in a low-power state, keeping the CPU occupied in a controlled way instead of leaving it idle.

Why ps aux Doesn’t Show PID=0 #

The ps aux command is designed to list user-space processes by default. These are processes that run in user mode, have their own address spaces, and are associated with user accounts. The idle process (PID=0) is a kernel thread, meaning it operates strictly in kernel mode, has no user-space context, and isn’t tied to any user.

Most standard ps invocations filter out kernel threads to avoid overwhelming users with internal kernel operations. If you want to see kernel threads (including PID=0, sometimes labeled [swapper] or [idle]), you can use flags like ps -eLf or ps axf—but even then, it might not be immediately obvious unless you know what to look for.

Does PID=0 Exit After System Initialization? #

Nope—PID=0 sticks around for the entire life of the system. Once the kernel finishes initializing and forks PID=1 (the user-space init process), PID=0 transitions into its idle role and never exits. It’s always waiting in the wings: whenever the CPU scheduler can’t find any active processes ready to run, it switches to PID=0 to handle those idle cycles.

Why Is It Called the "Idle Process" If It’s Always Running? #

The name refers to its purpose, not its state. It only runs when the CPU would otherwise be idle. As soon as another process needs CPU time, the scheduler pauses the idle process and gives the CPU to the active task. It doesn’t do any user-facing work; its job is to manage idle CPU cycles efficiently, preventing the CPU from entering unregulated states that could waste power or cause issues.

内容的提问来源于stack exchange，提问作者Infinite