Lines Matching refs:processor

17 fetch and execute instructions: hardware threads, if present, or processor
20 with it, there is an opportunity to save energy for the processor that it
22 instructions from memory and putting some of the processor's functional units
27 (from the kernel perspective) and ask the processor to use (or "enter") that
35 units: *governors* responsible for selecting idle states to ask the processor
45 select an idle state to ask the processor to enter in order to save some energy.
86 	processor holding the given CPU can be asked to enter).
113 	Called to select an idle state for the processor holding the (logical)
125 	the scheduler tick before asking the processor to enter the selected
128 	processor will be asked to enter the selected idle state without
131 	asking the processor to enter the idle state).
148 quality of service (PM QoS) constraints on the processor wakeup latency into
167 idle states that the processor hardware can be asked to enter shared by all of
189 	Maximum time it will take a CPU asking the processor to enter this idle
197 	"loop" that can be used in order to avoid asking the processor to enter
202 be ``NULL``, points to the routine to execute in order to ask the processor to
214 :c:member:`states` array representing the idle state to ask the processor to
270 lead to modifications of the list of available processor idle states (which can