Lines Matching refs:CPU

1 Interaction of Suspend code (S3) with the CPU hotplug infrastructure
6 I. How does the regular CPU hotplug code differ from how the Suspend-to-RAM
12 interactions involving the freezer and CPU hotplug and also tries to explain
16 What happens when regular CPU hotplug and Suspend-to-RAM race with each other
61   Common    |               before taking down the CPU             |
108                           Regular CPU hotplug call path
130   Common    |               before taking down the CPU
140                               regular CPU hotplug]
145 regular CPU hotplug and the suspend code path converge at the _cpu_down() and
147 in that during regular CPU hotplug, 0 is passed for the 'tasks_frozen'
163 II. What are the issues involved in CPU hotplug?
166 There are some interesting situations involving CPU hotplug and microcode
179    arch/x86/kernel/microcode_core.c helps in discovering the type of the CPU
189    image for each CPU (after appropriate CPU type/model discovery using
193 c. When a CPU is physically hot-unplugged and a new (and possibly different
194    type of) CPU is hot-plugged into the system:
196    In the current design of the kernel, whenever a CPU is taken offline during
197    a regular CPU hotplug operation, upon receiving the CPU_DEAD notification
198    (which is sent by the CPU hotplug code), the microcode update driver's
200    microcode image for that CPU.
202    Hence, when a new CPU is brought online, since the kernel finds that it
203    doesn't have the microcode image, it does the CPU type/model discovery
205    for that CPU, which is subsequently applied.
208    update driver's callback registered for CPU hotplug events) calls
211    have a valid microcode image. This ensures that the CPU type/model
212    discovery is performed and the right microcode is applied to the CPU after
218    Strictly speaking, during a CPU hotplug operation which does not involve
220    off during a CPU offline. They are just put to the lowest C-states possible.
223    image during the CPU offline operation.
234    In the current design of the kernel however, during a CPU offline operation
237    And during the CPU online operations (during resume/restore), since the
239    CPUs, it just applies them to the CPUs, avoiding any re-discovery of CPU
241    right for the CPUs or not (due to the above assumption that physical CPU
246 III. Are there any known problems when regular CPU hotplug and suspend race
251 1. When invoking regular CPU hotplug, the 'tasks_frozen' argument passed to
258    inappropriate code by the callbacks registered for such CPU hotplug events.
260 2. If a regular CPU hotplug stress test happens to race with the freezer due