Lines Matching refs:CPU

8 - **Initiating / Calling CPU**: The CPU which stackshot was called from.
9 - **Main CPU**: The CPU which populates workqueues and collects global state.
10 - **Auxiliary CPU**: A CPU which is not the main CPU.
16 When a stackshot is taken, the initiating CPU (the CPU from which stackshot was
21 a CPU is derecommended due to thermal limits or otherwise, it will still be
22 IPI'd into the debugger trap, and we want to avoid overheating the CPU).
24 On AMP systems, a suitable P-core is chosen to be the “main” CPU, and begins
26 global state (On SMP systems, the initiating CPU is always assigned to be the
27 main CPU).
29 The other CPUs begin chipping away at the queues, and the main CPU joins
32 are collated together by the caller CPU. The output is identical to
37 do its work - each CPU has its own execution context and no context switching
47 easier queue first, and P cores will work on the harder queue first. Once a CPU
50 If latency collection is enabled, each CPU will record information about its run
53 threads processed by the CPU during its run.
78 Each CPU will report information about its buffers in its
84 Each CPU needs its own kcdata descriptor, but we don't know exactly how big each
101 ⎢  CPU 0  ⎥
104 ⎢  CPU 1  ⎥
107 ⎢  CPU 2  ⎥
124 CPU which can be seen from a debugger.
137 before (with a single CPU/thread) - with the only difference being that we can
143 auxilliary CPU (i.e. a CPU other than the one which initiated the stackshot)
145 being held by the initiating CPU. To mitigate this, when a CPU panics during a
149 There are checks for this flag at various points in stackshot, and once a CPU
150 notices it is set, it will spin in place. Before the initiating CPU spins in