dev/dtrace/dtrace.c

274  *     etc.  Importantly, dtrace_lock is _not_ required when in probe context;
278  * (2) dtrace_provider_lock is required when manipulating provider state, or
279  *     when provider state must be held constant.
281  * (3) dtrace_meta_lock is required when manipulating meta provider state, or
282  *     when meta provider state must be held constant.
699 /* Avoid compiler warnings when assigning regs[rd] = NULL */
775 			 * that the counter is never zero when we have seen
2207 		 * value that defaults to 1 when not present.  If additional
2926 	 * ensures that we won't trip up when access checking tests the
4090 				 * coherence, however, is when the specified
4216 			 * (when we fetch addr from mstate->dtms_strtok)
6220 		 * when it next leaves the kernel.
7005 				 * when we're in the ACTIVE state.  If we're
7137 			 * we were processing when we experienced the error.
8570  * will need to grab the dtrace_lock when it reenters the framework through
13650 	 * Darwin's DEVFS layer acquired the minor number for this "device" when it called
14007 	cyc_time_t when;
14196 	when.cyt_when = 0;
14197 	when.cyt_interval = opt[DTRACEOPT_CLEANRATE];
14199 	state->dts_cleaner = cyclic_add(&hdlr, &when);
14205 	when.cyt_when = 0;
14206 	when.cyt_interval = dtrace_deadman_interval;
14209 	state->dts_deadman = cyclic_add(&hdlr, &when);
14375 			 * will remain a multiple of a megabyte when
15860 	 * In this case only, it is okay to have lazy dof when dof mode is DTRACE_DOF_MODE_LAZY_OFF
15907 				 * when we released the dtrace lock. We have to dump this generation,
16269  * when the kext is loaded in memory, but before calling the
16427 	 * cpu_lock here -- it is legal for cpu_lock to be held when loading a
16428 	 * module.  (In particular, this happens when loading scheduling
16794 		 * buffer will be freed when the consumer exits.)
17217 	 * Only relinquish control of the kernel debugger interface when there
19017 		 * For all queries, we return EINVAL when the user specified