Lines Matching full:enabling

94 	dtrace_id_t	dcpc_id;	/* probeid this request is enabling */
143 	 * enabling and therefore we just look for the first entry in  in dcpc_fire()
415  *	more existing events and we are adding a new enabling. Create a
418  *	enabling but we still have enablings whch are valid. Create a new
493 	 * If we already have an active enabling then save the current cpc  in dcpc_program_cpu_event()
567  * enabling is removed, the state byte is set to DCPC_INTR_INACTIVE to indicate
609  * called before enabling the first dcpc based probe.
627  * during removal of the last dcpc based enabling.
643  * dcpc_program_event() can be called owing to a new enabling or if a multi
648  * and a new request set which contains the new enabling and any old enablings
681 		 * If we add new enabling to the original one, the CPU should  in dcpc_program_event()
692 	 * If this enabling is being removed (in the case of a multi event  in dcpc_program_event()
693 	 * capable system with more than one active enabling), we can now  in dcpc_program_event()
754 	 * Locate this enabling in the first free entry of the active  in dcpc_enable()
805 		 * Before attempting to program the first enabling we need to  in dcpc_enable()
825 	 * enabling.  in dcpc_enable()
864  * If only one enabling is active then remove the context and free
900 	 * If this is the only enabling then stop all the counters and  in dcpc_disable()
919 		 * the enabling being disabled is not the last one. Remove this  in dcpc_disable()
920 		 * enabling and re-program the hardware with the new config.  in dcpc_disable()