Lines Matching refs:CPU

1 		CPU hotplug Support in Linux(tm) Kernel
4 		CPU Hotplug Core:
24 reporting and correction capabilities in processors. CPU architectures permit
25 partitioning support, where compute resources of a single CPU could be made
28 node insertion and removal require support for CPU hotplug.
31 provisioning reasons, or for RAS purposes to keep an offending CPU off
32 system execution path. Hence the need for CPU hotplug support in the
35 A more novel use of CPU-hotplug support is its use today in suspend
40 General Stuff about CPU Hotplug
74 CPU maps and such
91 migrated to another target CPU.
124 CPU Hotplug - Frequently Asked Questions.
126 Q: How to enable my kernel to support CPU hotplug?
127 A: When doing make defconfig, Enable CPU hotplug support
136 Q: What architectures support CPU hotplug?
137 A: As of 2.6.14, the following architectures support CPU hotplug.
184 Q: How do i logically offline a CPU?
193 You should now not see the CPU that you removed. Also online file will report
200 A: Some architectures may have some special dependency on a certain CPU.
204 specifications, we didn't have a way to change the target CPU. Hence if the
205 current ACPI version doesn't support such re-direction, we disable that CPU
234 Q: How do i find out if a particular CPU is not removable?
237 time that this CPU cannot be removed.
240 last CPU, this will not be permitted. You can find such failures by
243 Q: What happens when a CPU is being logically offlined?
248   CPU is being offlined while tasks are frozen due to a suspend operation in
250 - All processes are migrated away from this outgoing CPU to new CPUs.
251   The new CPU is chosen from each process' current cpuset, which may be
253 - All interrupts targeted to this CPU is migrated to a new CPU
254 - timers/bottom half/task lets are also migrated to a new CPU
259   CPU is being offlined).
263   running on behalf of this CPU that was offlined"
265 Q: If i have some kernel code that needs to be aware of CPU arrival and
313 A: Yes, CPU notifiers are called only when new CPUs are on-lined or offlined.
368 A: The following are what is required for CPU hotplug infrastructure to work
372     - __cpu_up()        - Arch interface to bring up a CPU
373     - __cpu_disable()   - Arch interface to shutdown a CPU, no more interrupts
377      - __cpu_die()      - This actually supposed to ensure death of the CPU.
379                           that implement CPU hotplug. The processor is taken
449 			debug_mesg CPU $ACTION event not supported