Lines Matching refs:CPU

2 Interaction of Suspend code (S3) with the CPU hotplug infrastructure
8 I. Differences between CPU hotplug and Suspend-to-RAM
11 How does the regular CPU hotplug code differ from how the Suspend-to-RAM
17 interactions involving the freezer and CPU hotplug and also tries to explain
21 What happens when regular CPU hotplug and Suspend-to-RAM race with each other
66   Common    |               before taking down the CPU             |
117                           Regular CPU hotplug call path
139   Common    |               before taking down the CPU
149                               regular CPU hotplug]
154 regular CPU hotplug and the suspend code path converge at the _cpu_down() and
156 in that during regular CPU hotplug, 0 is passed for the 'tasks_frozen'
173 II. What are the issues involved in CPU hotplug?
176 There are some interesting situations involving CPU hotplug and microcode
189    arch/x86/kernel/microcode_core.c helps in discovering the type of the CPU
199    image for each CPU (after appropriate CPU type/model discovery using
203 c. When a CPU is physically hot-unplugged and a new (and possibly different
204    type of) CPU is hot-plugged into the system:
206    In the current design of the kernel, whenever a CPU is taken offline during
207    a regular CPU hotplug operation, upon receiving the CPU_DEAD notification
208    (which is sent by the CPU hotplug code), the microcode update driver's
210    microcode image for that CPU.
212    Hence, when a new CPU is brought online, since the kernel finds that it
213    doesn't have the microcode image, it does the CPU type/model discovery
215    for that CPU, which is subsequently applied.
218    update driver's callback registered for CPU hotplug events) calls
221    have a valid microcode image. This ensures that the CPU type/model
222    discovery is performed and the right microcode is applied to the CPU after
228    Strictly speaking, during a CPU hotplug operation which does not involve
230    off during a CPU offline. They are just put to the lowest C-states possible.
233    image during the CPU offline operation.
244    In the current design of the kernel however, during a CPU offline operation
247    And during the CPU online operations (during resume/restore), since the
249    CPUs, it just applies them to the CPUs, avoiding any re-discovery of CPU
251    right for the CPUs or not (due to the above assumption that physical CPU
259 Are there any known problems when regular CPU hotplug and suspend race
264 1. When invoking regular CPU hotplug, the 'tasks_frozen' argument passed to
269    reflect the frozen state and the CPU hotplug callbacks which evaluate
272 2. If a regular CPU hotplug stress test happens to race with the freezer due