Lines Matching refs:CPU

28  * Virtual CPU management.
46 * The hypervisor has two notions of CPU states as represented in the store:
50 * "online": the VCPU is running. Corresponds to a CPU state other than
53 * Currently, only a notification via xenstore can bring a CPU into a
60 * play nice, we don't allow it. Thus, any attempt to power on/off a CPU is
66 * (since we are just about to remove its ability to run on a real CPU,
67 * possibly forever). However, an offline CPU in Solaris can take
82 * Thus, we set CPU_PHASE_WAIT_SAFE for every powered-on CPU, as well as
83 * poking them to make sure they're not blocked[1]. When every CPU has
85 * know we can suspend, or power-off a CPU, without problems.
88 * way to ensure that the CPU doesn't miss the state change before
150 if (cpu == CPU->cpu_id)
217 * Fill in the remaining CPU context and initialize it.
331 * CPU context just once. Once the initialisation succeeds, we never
435 * Reset this CPU's context. Clear out any pending evtchn data, since event
468 * Restore the context of a CPU during resume. This context is always
505 * Reach a point at which the CPU can be safely powered-off or
506 * suspended. Nothing can wake this CPU out of the loop.
514 cpu_phase[CPU->cpu_id] = CPU_PHASE_SAFE;
515 while (cpu_phase[CPU->cpu_id] == CPU_PHASE_SAFE)
535 if (cpu_phase[CPU->cpu_id] == CPU_PHASE_WAIT_SAFE)
551 if (cpu_phase[CPU->cpu_id] == CPU_PHASE_WAIT_SAFE)
562 (void) xen_vcpu_down(CPU->cpu_id);
603 if (cp == NULL || cp == CPU)
639 if (cp == NULL || cp == CPU)
644 * If we see a CPU in one of these phases, something has
674 ASSERT(CPU->cpu_id != cp->cpu_id);
883 * we cannot 'start' the boot CPU.
948 * Run the virtual CPU configuration on a separate thread to