Lines Matching refs:CPU
36 * the active CPU when we're in kmdb so we can handle things like page faults
52 * The last phase of boot-loaded KMDB activation occurs at non-boot CPU
53 * startup. We will be called on each non-boot CPU, thus allowing us to set up
54 * any watchpoints that may have been configured on the boot CPU and interpose
55 * on the given CPU's IDT. We don't save the interposed descriptors in this
62 * each CPU's IDT. We save the handlers we replace, both for deactivation and
66 * rather than just modifying the IDT table from the CPU running kdi_activate().
255 kdi_kgates[i] = CPU->cpu_m.mcpu_idt[vec];
382 * Activation for CPUs other than the boot CPU, called from that CPU's
384 * boot CPU, so we don't want to do it again. Saving the handlers from this
385 * CPU's IDT would actually be dangerous with the CPU initialization method in
387 * the IDTs for slave CPUs by copying the one used by the boot CPU, which has
398 kdi_cpu_debug_init(&kdi_cpusave[CPU->cpu_id]);
518 * State has been saved, and all CPUs are on the CPU-specific stacks. All