Lines Matching refs:CPU
44 * DTrace CPU Performance Counter Provider
47 * The DTrace cpc provider allows DTrace consumers to access the CPU
48 * performance counter overflow mechanism of a CPU. The configuration
51 * hardware causes a counter on each CPU to begin counting events of the
60 * subset of the events available for a given CPU. However, when overflow
78 * consumers of the kernel CPU performance counter subsystem (e.g. cpustat(1M)).
150 CPU->cpu_cpcprofile_pc,
151 CPU->cpu_cpcprofile_upc, 0, 0, 0);
168 CPU->cpu_cpcprofile_pc,
169 CPU->cpu_cpcprofile_upc, 0, 0, 0);
344 if (CPU->cpu_cpcprofile_pc == 0) {
387 * are dealing with a CPU that is just coming online.
530 * Leave this CPU alone if it's already offline.
553 * per-CPU dcpc interrupt state byte. The purpose of the state byte is to
555 * changes made to the CPU performance counter subsystem by the dcpc provider.
676 * If we come here when the first event is programmed for a CPU,
679 * context on the CPU.
681 * If we add new enabling to the original one, the CPU should
712 * configure the requests in the set for the CPU and not because of
855 * collection for every CPU.
938 * collection for every CPU
957 * CPU if we are actively tracing.
966 * on this CPU while we disable it.
987 * This CPU is being initialized or brought online so program