Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Even if no user process is running, don't the kernel processes keep the CPU active enough so as to prevent it from entering a deeper C state like C1 or C2 ?

share|improve this question
this is a good question, but I'm not so sure it's really a sysadmin question. It's really a question for kernel programmers with hardware experience.. – Jeff Atwood Jan 27 '12 at 0:03
@JeffAtwood: The mechanics of how to implement this functionality in an OS kernel are probably off-topic, but I'd say that a sysadmin needs to know how the hardware power management functionality in their systems works ( – Evan Anderson Jan 27 '12 at 1:44

CPUs (or individual cores) can be put into "deep" C-states by an OS kernel.

You're thinking that the processor "puts itself to sleep" when it "detects" inactivity. This isn't how it works. The OS scheduler determines system idle percentage based on the amount of time spent in the system idle loop to detect system inactivity. The CPU itself (in x86 land, at least) doesn't know "what" it's executing and doesn't have context to "detect" idle cycles on its own.

The system firmware contains ACPI tables that define the power management capabilities of the hardware. These tables are read by the OS when it starts up. The OS kernel processor driver (or whatever the analog is to that for a given operating system) is responsible for monitoring the CPU workload and instructing the hardware to put the CPU into a power management state selected from the firmware ACPI tables.

Microsoft has an article describing power management in Windows 7 and Server 2008 R2. IBM has an article (likely dated, however) about the CPUfreq system in Linux.


It's worth pointing out that many server computers have an onboard hardware-based mechanism to monitor and manage CPU states. This isn't being done "in the CPU" either, but rather is taking the place of the OS power and performance management functionality. It's been my experience that this often yields power savings but at the expense of system performance.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.