Lines Matching full:reprogramming

266 		 * so we keep it on the same CPU. No hassle vs. reprogramming  in switch_hrtimer_base()
561  * cpu_base::*expires_next right away, reprogramming logic would no longer
788 	 * function call will take care of the reprogramming in case the  in retrigger_next_event()
901 	 * before reprogramming. Nothing to do here.  in update_needs_ipi()
1106  * reprogram to zero. This is useful, when the context does a reprogramming
1149 		 * Remove the timer and force reprogramming when high  in remove_hrtimer()
1151 		 * CPU. If we remove a timer on another CPU, reprogramming is  in remove_hrtimer()
1153 		 * reprogramming happens in the interrupt handler. This is a  in remove_hrtimer()
1160 		 * If the timer is not restarted then reprogramming is  in remove_hrtimer()
1203 	 * reprogramming needs to be triggered, even if the next soft  in hrtimer_update_softirq_timer()
1227 	 * timer then this might end up reprogramming the hardware twice  in __hrtimer_start_range_ns()
1230 	 * and enforce reprogramming after it is queued no matter whether  in __hrtimer_start_range_ns()
1248 	 * skip reprogramming, keep the timer local and enforce  in __hrtimer_start_range_ns()
1249 	 * reprogramming later if it was the first expiring timer.  This  in __hrtimer_start_range_ns()
1295 	 * reprogramming on removal and enqueue. Force reprogram the  in __hrtimer_start_range_ns()
1899 	/* Reprogramming necessary ? */  in hrtimer_interrupt()